Hi Robby -
[quoted text, click to view] >Is it? If not, what other mechanisms are available to signal client apps of
>sundry DB goings-on?
Given the 5 sentence description in your original post - as good as
they are - I wouldn't hazard a recommendation; it's just not enough
info. However, from the sounds of it I suspect that SQL Dependency may
be a better option for you.
[quoted text, click to view] >I have no idea what that means. Where would I learn more?
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlntsv9/html/01fb3263-0876-4058-b7c1-2aa24ba39e7d.htm
Additionally Shyam Pather's bood has a section on it if memory serves
me (I don't have it in front of me at the moment). It's written for
v2.0, but many of the same concepts should apply.
[quoted text, click to view] >SQL Server 2005
Then SQLDependency is an option for you.
HTH...
--
Joe Webb
SQL Server MVP
http://www.sqlns.com ~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 I support PASS, the Professional Association for SQL Server.
(
www.sqlpass.org)
On Fri, 27 Jan 2006 10:02:05 -0600, "Robby Tanner"
[quoted text, click to view] <robby_tanner@hotmail.com> wrote:
>
>"Joe Webb" <joew@webbtechsolutions.com> wrote in message
>news:9e0kt1p3i0ujr8hddh7nkakhn0jhtes7c5@4ax.com...
>
>> From the way you've described, I think Notification Services could do
>> exactly what you're tasked with accomplishing. The big question is: is
>> it the best tool?
>
>Is it? If not, what other mechanisms are available to signal client apps of
>sundry DB goings-on?
>
>
>> With SQLNS, you'd need to create a custom delivey
>> channel to communicate with your attached clients.
>
>I have no idea what that means. Where would I learn more?
>
>> Are you using SQL Server 2000 or 2005? If the latter, you may also
>> want to check out SqlDependency and Query Notifications
>> (
http://msdn2.microsoft.com/en-us/library/ms179575.aspx) as another
>> possibility.
>
>SQL Server 2005
>
>Regards,
>Rob
