If the 3rd party database is a SQL Server database, you could add an "Extended Stored Procedure" to the database (written in unmanaged C++) that could notify your software of the required database event(s).
There was a brief discussion on this topic in February: http://discuss.develop.com/archives/wa.exe?A2=ind0202A&L=DOTNET&D=0&P=91 134 If the db is not SQL Server, you'll have to check your database's documentation for an equivalent to Extended Stored Procedures. Note that this doesn't require a change to the software managing the data, just to the database itself (again assuming it's a SQL Server db). I also understand that the next version of SQL Server will allow Extended Stored Procedures to be written in managed code... can't wait. Martin. > -----Original Message----- > From: Moderated discussion of advanced .NET topics. [mailto:ADVANCED- > [EMAIL PROTECTED]] On Behalf Of Wayne Enis > Sent: 03 July 2002 14:50 > To: [EMAIL PROTECTED] > 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.
