Thanks Joe ... this is pretty close to what we're looking for - great
Let me ask you if there's a way to take SQL Server 2000 and have it send out
"notifications" to an application that we would create that simply listens
for these (or "events" in the sense of the word like .NET programatic events
used to indicate something has happened, such as a user clicked a button, a
Form changed size, or a communications channel was closed, as quick
Instead of each table firing a trgger which adds a row into a "notification
table" for each added/modified/deleted row (as described in the article), and
then our program "polling" the notification table to determine what happened
... what we're attempting to do is create an application that is smart enough
to tell us a row of data changed, instead of the application having to poll
the DB. For performance reasons we're hoping to find a way to stay informed
of database changes, but without polling. These notifications could be in
the form of e-mails, which was mentioned in the SQL 2005 documentation I
read, but we'd prefer for the notfication to be in the form of an actual
"event" to keep performance at the highest level possible.
Perhaps we'd have to create an application that resides of the SQL 2000 box,
that would listen for these notidications or events, then our "listening
applicaiton" could fire real .NET events from the SQL 2000 box to our other
application which is interested in these changes of data????
Forgive my silly ideas - we're just trying to determine how best to
I would love to hear your thoughts about what I've written here. Again,
thanks for you help with this Joe,
Markus Anderson (a.k.a the Moble Man)
"Joe Webb" wrote:
> Something like this, perhaps?
> Joe Webb
> SQL Server MVP
> Get up to speed quickly with SQLNS
> I support PASS, the Professional Association for SQL Server.
> On Wed, 27 Sep 2006 15:19:01 -0700, MobileMan
> <[email protected]> wrote:
> >What is the best way to be notified, from SQL Server 2000, that a row was
> >added, deleted, or modified in another application?
> >I'm a competent C# developer, but a "babe in the woods" when it comes to SQL
> >Server. I have been reading about the Notification "engine" in SQL Server
> >2005 and am looking for something similar for a SQL Server 2000 setup.
> >We have an application that uses SQL Server 2000 for data storage. When a
> >new record is created or deleted, or an existing record modified we want to
> >somehow "notify" another application of this fact.
> >In a perfect world we would sent an "event" from SQL Server 2000 to the 2005
> >server, or even better to another application that is listening for events
> >from the 2000 server. If our "listening application" can receive the event
> >then we can handle things from there.
> >Any suggestions or thoughts are greatly appreciated. Thanks for your advice.