microsoft.public.sqlserver.notificationsvcs
[Top] [All Lists]

Re: API or stored procedures....which is better

Subject: Re: API or stored procedures....which is better
From:
Date: 25 Jan 2006 05:36:21 -0800
Newsgroups: microsoft.public.sqlserver.notificationsvcs
So basically, this improvement in subscription management via SQL is
only really meant for development & testing.  So if our data sits in
another database, Microsoft doesn't want us triggering over to these
views to add subscribers & subscriptions, right?

Joe Webb wrote:
> For v2.0, the *only* supported way to management subscription data is
> via the API. There are lots of dynamically created views that cover
> the base tables so accessing those tables directly or via sprocs is
> not supported.
>
> For 2005, we have been given the ability to use some view to
> management subscriptions.
>
> I've blogged about each of these scenarios here.
>
> Creating Subscribers in v2.0
> (http://sqlns.blogspot.com/2005/09/creating-subscribers-in-v20.html)
>
> Creating Subscribers in 2005
> (http://sqlns.blogspot.com/2005/10/creating-subscribers-in-2005.html)
>
>
> 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 24 Jan 2006 12:57:48 -0800, [email protected] wrote:
>
> >I've read (or heard - can't remember) that we should use the API to
> >handle subscription management.  Why not just the Stored procedures?
> >If we've got our data in other databases, why not just link to the NS
> >server, and execute the SP to get the subscription data over?


<Prev in Thread] Current Thread [Next in Thread>