|
You have to write them somewhere in case you can't reach the SQL server.
Direct communication from a trigger strikes me as a bad idea in general.
Consider there's no way to handle a set of changes being rolled back; as
the trigger doesn't get called again. Unless ARDGATE supports distributed
transactions (XA)?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.