I think a trigger in SQL is going to be your best bet. Create an extended stored procedure that calls out to an external COM object. Or, create an exe that is called from SQL. I think the COM method is faster, as the COM object runs under the SQL process, so there is less startup overhead.
If you absolutely can't do anything to the DB, you may be able to put a FileSystemWatcher on the SQL server data and log files. I haven't checked, but they shouldn't change unless there is an update. Erick ----- Original Message ----- From: "Wayne Enis" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 03, 2002 6:49 AM Subject: [ADVANCED-DOTNET] Watching for SQL Events I'm after some functionality similar to the FileSystemWatcher component, but watching for events within a SQL database, notifying me of any insert, update or delete events.Is it possible to trap SQL events within .net. The database i need to watch is a 3rd party product, where i have not control over the software managing the data, the best i could probably hope for is that i could create new triggers. Any ideas anyone ?? Wayne You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
