Equivalent to database events

[Chloe Crowder]

Hi

we are considering porting an application from Ingres to SQL Server.
Part of the application uses a feature of Ingres called database
events. These allow a application to monitor for an event happening in
the database, e.g. a user enters a record meeting certain conditions,
the database raises an event including a record ID, and a client
application sees the event (without continual explicit polling), reads
the new record and starts processing it.

Any idea what the equivalent functionality would be in SQL Server
2000, or are applications simply not done that way?

TIA

Chloe Crowder
The British Library

[Greg D. Moore \(Strider\)]

"Chloe Crowder" <ch***********@bl.uk> wrote in message
news:f2**************************@posting.google.c om...

Hi

we are considering porting an application from Ingres to SQL Server.
Part of the application uses a feature of Ingres called database
events. These allow a application to monitor for an event happening in
the database, e.g. a user enters a record meeting certain conditions,
the database raises an event including a record ID, and a client
application sees the event (without continual explicit polling), reads
the new record and starts processing it.
Sounds like you might be able to use INSERT/UPDATE/DELETE triggers.


Any idea what the equivalent functionality would be in SQL Server
2000, or are applications simply not done that way?

TIA

Chloe Crowder
The British Library

[Christian Maslen]

> we are considering porting an application from Ingres to SQL Server.

Part of the application uses a feature of Ingres called database
events.

Database events are one of the few things I've seen in Ingres that I'd
never come across before. I don't think SQL Server 2000 has an
equivalent feature, but looking at the feature list for Yukon it
appears to be coming:

http://msdn.microsoft.com/library/de...ovyukondev.asp

Check out the paragraph on the SQL Service Broker.

Christian.

[Joe Maloney]

There are things called triggers ('on insert' in this case) that can
kick off processing as you describe.

There are other techniques available, but more information about your
application/process would be needed before I put the other foot in my
mouth.
ch***********@bl.uk (Chloe Crowder) wrote in message news:<f2**************************@posting.google. com>...

Hi

we are considering porting an application from Ingres to SQL Server.
Part of the application uses a feature of Ingres called database
events. These allow a application to monitor for an event happening in
the database, e.g. a user enters a record meeting certain conditions,
the database raises an event including a record ID, and a client
application sees the event (without continual explicit polling), reads
the new record and starts processing it.

Any idea what the equivalent functionality would be in SQL Server
2000, or are applications simply not done that way?

TIA

Chloe Crowder
The British Library

[Chloe Crowder]

ch**************@techie.com (Christian Maslen) wrote in message

Database events are one of the few things I've seen in Ingres that I'd
never come across before. I don't think SQL Server 2000 has an
equivalent feature, but looking at the feature list for Yukon it
appears to be coming:

http://msdn.microsoft.com/library/de...ovyukondev.asp

Check out the paragraph on the SQL Service Broker.

Christian.

Thanks for this Christian, it does look (at first glance) very similar
to what we've been using in Ingres.

Chloe

[Christian Maslen]

ch***********@bl.uk (Chloe Crowder) wrote in message news:<f2**************************@posting.google. com>...

ch**************@techie.com (Christian Maslen) wrote in message

Database events are one of the few things I've seen in Ingres that I'd
never come across before. I don't think SQL Server 2000 has an
equivalent feature, but looking at the feature list for Yukon it
appears to be coming:

http://msdn.microsoft.com/library/de...ovyukondev.asp

Check out the paragraph on the SQL Service Broker.

Christian.

Thanks for this Christian, it does look (at first glance) very similar
to what we've been using in Ingres.

Chloe

Are you just porting the DB and keeping OpenROAD? Or is it a complete
rewrite? The closest you can get without waiting for Yukon is to use a
message queuing package. I've not done anything in this area, but I
think the MS option comes out of the box with Win2k servers.

Christian.