I have need to call a webservice when a particular column in a table changes. I can handle the deciding of which column changed in the insert/update/delete but I’m not sure how I should call the webservice.
The webservice is offsite, we have a little control over it (we can ask for changes and get a reasonably quick response) but the service is a work in progress and so is our code.
SQL Server version is 2005.
Update: much of the business logic in this app is in the SQL layer. No way for me to change it and complaining about it is not a good use of my time. It is what it is. Wish that there was a business logic layer but it’s partially in the pres layer and partially in the SQL layer. A trigger in the table is the most central place.
Don’t. The overhead of a web service is incompatible with the execution processing cycles of a database. Take it out of the database and (preferably) make it asynchronous – see references to ‘queue/monitor’ in various answers below.
Probably a Duplicate question, too.