June 17, 2003 at 2:28 pm
I’m new to SQL, so this is possibly a daft question.
I have a trigger on a TABLE that informs a service whenever a record has changed in this table ( we call the service the ‘Notification Service’). This service is responsible for informing all our client applications that there has been a change in the DB. The clients then query the DB for the changed record.
The process that changes the records in this table does so in batches. And only after the completion of a batch are the changes committed. If this batch takes a long time, then our clients get informed of a change before the change is committed and try to query the DB. The clients then hang until the changes are committed.
We do not have the option of changing the ‘Notification Service’
The question is. Can I get the trigger to fire for each changed record when the changes are committed rather than on INSERT, UPDATE or DELETE?
Thanks
June 17, 2003 at 4:33 pm
Hmmm... Could you call the Notification Service at the end of your batch instead of resorting to a trigger? Perhaps log the changes in another table and then let the Notification cycle through the changed records. Alternatively, could the client applications query the changed records in batches? Or, and obviously I don't know much of anything about your operation, could this process be a candidate for replication?
Is there anything else you can give us to flesh out your situation?
SJTerrill
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply