January 11, 2011 at 8:08 am
To make the trigger and email sending more 'bullet proof' and completely asynchronous, I would simply put the requisite PK (and perhaps some payload if you must) into a driver table. Then have a secondary mechanism that sweeps the driver table to dequeue and process emails as it wishes. This way the initial transaction will finish VERY quickly and have no concerns about email/SSB availability, etc.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing post 16 (of 15 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy