Depends on how scalable you want it to be. The original poster did mention
"like FileWatcher" which sounds like one client. Notification services would be
overkill in that situation. But imagine sending change notifications to many clients
by sequentially firing through a trigger after looking up which clients are to be
notified..., the trigger time would be too long.
Although notification services comes with an SMTP delivery channel, think MSMQ
(or a private protocol that does IP multicast) delivery channel...its delivery channel
arhcitecture uses a provider model.
BTW, Rob Howard did post some code (on gotdotnet, I think) that fires a change
to a file through a trigger to notify ASP.NET (watching through file watcher) for
cache invalidation purposes. But he also said it wouldn't scale. ;-)
Bob Beauchemin
[EMAIL PROTECTED]
-----Original Message-----
From: Howard Dierking [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 05, 2002 4:54 AM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] Watching for SQL Events
I looked at the SQL notification services white paper earlier and honestly,
this seems kind of off target for something as simple as raising an event to
client code (it looks like the service compares more to SQL mail). Am I
missing something here?
_howard
-----Original Message-----
From: Wayne Enis [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 05, 2002 2:01 AM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] Watching for SQL Events
Thanks, i'm signing up for the beta program now ! I think i'll just go
along the SP route for now, don't really want to put beta services on my
production servers.
Wayne
-----Original Message-----
From: Niels Berglund [mailto:[EMAIL PROTECTED]]
Sent: 03 July 2002 18:22
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] Watching for SQL Events
Apart from implementing an extended sp or using sp_OACreate and friends
(allow you to call COM objects) you could use a new service for SQL
Server called SQL Server Notification Services. It's a service which
allows you to catch various types of events (both from SQL Server as
well as other places) and notify interested parties/apps of the events.
More info at: http://www.microsoft.com/sql/NS/overview.asp
Niels
Developmentor
http://staff.develop.com/nielsb
> -----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.
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.
You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
