|
|
You're in the
sql server notification services
group:Customizing NS instance db - opinions?
sql server notification services:
I want just a few more features in my notification application that I
haven't seen in SQL NS - the main feature we're desiring is the ability for subscribers to maintain their subscriptions. I know this needs to happen in a Sub. Management interface, but here's what I'm getting at. If all I want is simply to add one table into the instance DB to store username, password, firstname, lastname, and have subscriberID as the primary key, is this a problem? Also probably some custom stored procedures. I didn't want to have to have a profile/account/login sort of database elsewhere and try & maintain duplicate data between that DB & my NS DB. So theoretically, the user could login to a web site (hitting my custom tables & stored procedures to validate their account/password). Then the site would use all the normal views avaialable from NS to allow the user to manage their own subscriptions. Any problems with this? I would still be using Microsoft approved ways to manage subscribers, subscriber devices, and subscriptions - through their views. Everything would be in one database.
Are you using SQL Server 2005? If so, you can create 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) [quoted text, click to view] On 28 Feb 2006 16:38:10 -0800, unc27932@yahoo.com wrote:
>I want just a few more features in my notification application that I >haven't seen in SQL NS - the main feature we're desiring is the >ability for subscribers to maintain their subscriptions. I know this >needs to happen in a Sub. Management interface, but here's what I'm >getting at. If all I want is simply to add one table into the instance >DB to store username, password, firstname, lastname, and have >subscriberID as the primary key, is this a problem? Also probably some >custom stored procedures. > >I didn't want to have to have a profile/account/login sort of database >elsewhere and try & maintain duplicate data between that DB & my NS >DB. > >So theoretically, the user could login to a web site (hitting my custom >tables & stored procedures to validate their account/password). Then >the site would use all the normal views avaialable from NS to allow the >user to manage their own subscriptions. Any problems with this? I >would still be using Microsoft approved ways to manage subscribers, >subscriber devices, and subscriptions - through their views.
We are using 2005. Thanks Joe. I've already created the instance &
application databases. Is it better to... 1. First create my custom database, then create the NS instance & applicaiton dbs, in the existing db OR 2. First create the NS application & db, then customize. Presently I'm doing #2, simply b/c I only have 1 extra table & a few SPs.
My only issue with #1 is that my SPs and table triggers use the views
to manage subscribers. For example....a web user comes to the site, creates an account with a username, password, firstname, lastname, emailaddress etc. I insert this into my custom table (the profile/account tracker table), then an insert trigger inserts into the NSSubscriberView with the user marked as disabled, and inserts into the NSSubscriberDeviceView with their default email address. Then a validation email is sent out saying - hey you registered, click here to confirm, and the page they get sent to updates the NSSubscriberView and sets them to be enabled. I could only set up these triggers & sps after already creating the NS databases, b/c they depended on the NS views. If I create an existing database (which would really only have 1 table) and try to add in my custom trigger, SP, etc., and there's no NS views there, I won't be able to. #1 & #2 seem to produce the same end result to me. I'm not altering any of the NS code. I just have added one table, several stored procedures, and a trigger on my custom table (not on the NS stuff). I could see how if I was messing around with the NS code/tables then this would be dangerous. Any more thoughts?
The only supported/recommended way of doing #2 is to do all
customizations through the ICF & ADF. So I'd recommend going with #1. HTH.... Joe -- 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) [quoted text, click to view] On 1 Mar 2006 06:18:57 -0800, unc27932@yahoo.com wrote:
>We are using 2005. Thanks Joe. I've already created the instance & >application databases. Is it better to... > >1. First create my custom database, then create the NS instance & >applicaiton dbs, in the existing db > >OR > >2. First create the NS application & db, then customize. > >Presently I'm doing #2, simply b/c I only have 1 extra table & a few
Either should work, then. Just take care when you update your instance
that your changes are not lost along the way. 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) [quoted text, click to view] On 1 Mar 2006 06:37:01 -0800, unc27932@yahoo.com wrote:
>My only issue with #1 is that my SPs and table triggers use the views >to manage subscribers. For example....a web user comes to the site, >creates an account with a username, password, firstname, lastname, >emailaddress etc. I insert this into my custom table (the >profile/account tracker table), then an insert trigger inserts into the >NSSubscriberView with the user marked as disabled, and inserts into the >NSSubscriberDeviceView with their default email address. Then a >validation email is sent out saying - hey you registered, click here to >confirm, and the page they get sent to updates the NSSubscriberView and >sets them to be enabled. I could only set up these triggers & sps >after already creating the NS databases, b/c they depended on the NS >views. If I create an existing database (which would really only have >1 table) and try to add in my custom trigger, SP, etc., and there's no >NS views there, I won't be able to. > >#1 & #2 seem to produce the same end result to me. I'm not altering >any of the NS code. I just have added one table, several stored >procedures, and a trigger on my custom table (not on the NS stuff). I >could see how if I was messing around with the NS code/tables then this >would be dangerous. >
Yes - definitely being sure to back everything up & script it out, etc.
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |