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

Re: Some general questions

Subject: Re: Some general questions
From: Joe Webb
Date: Mon, 12 Dec 2005 21:00:03 -0600
Newsgroups: microsoft.public.sqlserver.notificationsvcs
I absolutely agree with Kate's recommendations. 

BTW - in SQL Server 2005, we're no longer required to use a database
created by SQLNS; we can tell it to place the instance and application
database objects in an existing database. 



-- 
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 12 Dec 2005 13:25:36 -0800, "kate" <[email protected]> wrote:

>although with NS it looks like a duplicate user structure, actually
>very little user data is held other than the key subscriberid and an
>on/off switch. the main information is the devices for each user. NS
>needs a local key structure for subscribers cos existing apps could use
>all sorts of id's for the individual so with a generic architecture you
>would always have this sort of internal subscriber table. Just cross
>reference it to your existing apps is the easiest way to link the two
>together and is very straightforward to maintain. In your own app just
>add a table for the subscriberid - userid columns and off you go.
>
>I would keep your 'real' user records in your own business app and
>connect them to these artificial 'subscribers' structure. that gives
>you lots of flexibility for future development and protects your app
>from changes that will be made to NS in the future.
>
>kate p

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