Catch a trigger in .net?

[Poohface]

I think I might be wishing for the impossible here or at least waiting
for Yukon, but I'm wondering if it is possible to catch a SQL Server
trigger as an event in a vb .net app? Not sure what would be involved
or how it would work considering the fact that the DB is disconected
from the client unless a read or write is in progress.

The reason I ask:

I have an app I wrote that shows current open service calls for a
company, and allows them to dispatch them. To update the open calls
list right now I have a timer that checks for new open calls every
30secs and a manual refresh button. Would be cool if the DB could fire
a trigger when a new call was added that my app could catch and know
that it had to update the list of open calls. Although I have been
carefull not to cause any excess network traffic, I would much rather
have it only bother the server for new calls when needed.

Ideas are greatly welcomed.

Norst

 

[Guest]

You can have the trigger fire off a process that adds the new request to a
queue. In SQL Server 2005, you also have the Service Broker, which gives you
an even better model, of course. With the 2.0 Framework, you can also set up
data caching, but it will poll, albeit automatically, when you are using SQL
Server 2000.


---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************