|
I'm working a program that will send an e-mail based on a insert trigger on Table A. In the trigger, we also look up Table B. The problem is that Table B is updated/inserted after Table A, and the update is running in the same thread. I was thinking of creating SQL proc (proc would sleep for 2 seconds) and call it from the trigger. Is it possible to force the procedure to run in a different thread (so it's not blocked by the sleep etc)?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
