> Try this link. It should give you everything you need:
>
[quoted text clipped - 6 lines]
>> Any help would be greatly appreciated.
>> Leila
Here is a link to a full MS Technical Overview of NS for SS2k. It does not
require Service Broker. The article talks about queuing of messages. Changes
to tables in NS would be an Event that a subscriber would subscribe to. Code
would have to be written that captures the event. This link gives a lot of
information on the architecture.
http://www.microsoft.com/technet/prodtechnol/sql/2000/evaluate/sqlnsto.mspx
Here is another link containing links to more info\resources including
WebCasts, code, etc.
http://search.technet.microsoft.com/search/Default.aspx?query=notification%20ser
vices&brand=technet&locale=en-us&refinement=00&lang=en-us
-Mike
> Thanks Mike,
> As far as I know, SQL Service Broker is required to notify clients about
[quoted text clipped - 11 lines]
> >> Any help would be greatly appreciated.
> >> Leila
Bob Beauchemin - 20 Jul 2007 22:57 GMT
SQL Server Notification Service != Query Notifications. It's more of an
overloading of the word "notification". Not to say you couldn't code
something up using triggers and MSMQ and SQLNS, but it's not the same
feature.
The did implement "ASP.NET cache sync" on top of SQL2K, but its an entirely
different implementation than SQL2K5. It uses polling rather than broker and
query notifications. But query notifications itself requires SQL2K5.
Cheers,
Bob Beauchemin
> Here is a link to a full MS Technical Overview of NS for SS2k. It does not
> require Service Broker. The article talks about queuing of messages.
[quoted text clipped - 29 lines]
>> >> Any help would be greatly appreciated.
>> >> Leila