Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a table that will receive messages from a 3rd party software, I need a triggering mechanism to call my dotnet code. What are are the pros and cons of a trigger calling a SQLCLR which then could call a web service for example vs just having my code poll the table for changes. Is suspect the average load of the table will be very little, maybe a few thousand transactions a day.
You don’t say what version of SQL Server you’re using, but if it’s 2005+, Service Broker was made for this. In your trigger, put a (short) message on the queue. Have your service execute a WAITFOR on the queue which will then trigger a RECIEVE to grab the message. Better than spinning cycles seeing if there’s nothing to do.