|
|
You're in the
sql server notification services
group:Various questions....updating instance, vacuuming, and emails....
sql server notification services:
for example you update a subscription class. Is any data lost? Are tables dropped & readded? I had a situation where I updated my instance, and some new tables were created called NS<subscriptionclass>Old. Then they weren't purged during the update. Then when I updated the instance again, the update failed b/c it was trying to create these "Old" tables again but they were never dropped on the first update. 2. Vacuuming - anyone want to give a brief 101 on this? How long event data stays present, how long till it's purged? I'm assuming it's a setting you can adjust in the ADF, but haven't looked yet. 3. Should I check the DeviceAddress column in the NSSubscriberDevice view, via my subscription management, to see if an email address already exists before I add it again? I'm trying to plan for if someone registers under accountname1/emailaddress1, and then they come back and create another account under accountname2/emailaddress1.
One more question.....
If a subscriber is disabled (select enabled from nssubscriberview = 0) but their subscriptions are Enabled (select enabled from NS<subscriptionclass>View = 'Enabled'), what happens? They get no emails? I'm trying to figure out if I disable a subscriber do I need to also go disable all their subscriptions as well manually, or does NS just skip over any subscribers that are disabled and pay no attention to their subscriptions? [quoted text, click to view] unc27932@yahoo.com wrote:
> 1. When you update an instance and tables get new columns, etc. - say > for example you update a subscription class. Is any data lost? Are > tables dropped & readded? I had a situation where I updated my > instance, and some new tables were created called > NS<subscriptionclass>Old. Then they weren't purged during the update. > Then when I updated the instance again, the update failed b/c it was > trying to create these "Old" tables again but they were never dropped > on the first update. > > 2. Vacuuming - anyone want to give a brief 101 on this? How long > event data stays present, how long till it's purged? I'm assuming it's > a setting you can adjust in the ADF, but haven't looked yet. > > 3. Should I check the DeviceAddress column in the NSSubscriberDevice > view, via my subscription management, to see if an email address > already exists before I add it again? I'm trying to plan for if > someone registers under accountname1/emailaddress1, and then they come > back and create another account under accountname2/emailaddress1.
Back to the top here - for anyone who has some answers to these
questions. I found the answer to #1. When you update an application, if you make a change to the subscriptionclasses those tables are recreated, and the old data is stored in: NS<subscriptionclass>Old ( http://msdn2.microsoft.com/en-US/library/ms171329(SQL.90).aspx ). Does anyone have the answers to the other questions? [quoted text, click to view] unc27932@yahoo.com wrote:
> One more question..... > > If a subscriber is disabled (select enabled from nssubscriberview = 0) > but their subscriptions are Enabled (select enabled from > NS<subscriptionclass>View = 'Enabled'), what happens? They get no > emails? I'm trying to figure out if I disable a subscriber do I need > to also go disable all their subscriptions as well manually, or does NS > just skip over any subscribers that are disabled and pay no attention > to their subscriptions? > > > unc27932@yahoo.com wrote: > > 1. When you update an instance and tables get new columns, etc. - say > > for example you update a subscription class. Is any data lost? Are > > tables dropped & readded? I had a situation where I updated my > > instance, and some new tables were created called > > NS<subscriptionclass>Old. Then they weren't purged during the update. > > Then when I updated the instance again, the update failed b/c it was > > trying to create these "Old" tables again but they were never dropped > > on the first update. > > > > 2. Vacuuming - anyone want to give a brief 101 on this? How long > > event data stays present, how long till it's purged? I'm assuming it's > > a setting you can adjust in the ADF, but haven't looked yet. > > > > 3. Should I check the DeviceAddress column in the NSSubscriberDevice > > view, via my subscription management, to see if an email address > > already exists before I add it again? I'm trying to plan for if > > someone registers under accountname1/emailaddress1, and then they come > > back and create another account under accountname2/emailaddress1.
1. Answered by CoreyB.
2. Check out the following elements of the ADF. <Vacuum> <RetentionAge> <VacuumSchedule> 3. I typically do since I use the email address (device address) as a way to uniquely identify my subscribers. 4. According to BOL: The Enabled field is used to enable or disable a subscriber within the Notification Services system. When the Enabled status is true, the subscriber is active, and the subscriber's subscriptions can generate notifications. When the Enabled status is false, the subscriber is inactive and the subscriber's subscriptions will not generate notifications. 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 27 Mar 2006 13:49:35 -0800, "CoreyB" <unc27932@yahoo.com> wrote:
>Back to the top here - for anyone who has some answers to these >questions. I found the answer to #1. When you update an application, >if you make a change to the subscriptionclasses those tables are >recreated, and the old data is stored in: NS<subscriptionclass>Old ( >http://msdn2.microsoft.com/en-US/library/ms171329(SQL.90).aspx ). > >Does anyone have the answers to the other questions? > > >unc27932@yahoo.com wrote: >> One more question..... >> >> If a subscriber is disabled (select enabled from nssubscriberview = 0) >> but their subscriptions are Enabled (select enabled from >> NS<subscriptionclass>View = 'Enabled'), what happens? They get no >> emails? I'm trying to figure out if I disable a subscriber do I need >> to also go disable all their subscriptions as well manually, or does NS >> just skip over any subscribers that are disabled and pay no attention >> to their subscriptions? >> >> >> unc27932@yahoo.com wrote: >> > 1. When you update an instance and tables get new columns, etc. - say >> > for example you update a subscription class. Is any data lost? Are >> > tables dropped & readded? I had a situation where I updated my >> > instance, and some new tables were created called >> > NS<subscriptionclass>Old. Then they weren't purged during the update. >> > Then when I updated the instance again, the update failed b/c it was >> > trying to create these "Old" tables again but they were never dropped >> > on the first update. >> > >> > 2. Vacuuming - anyone want to give a brief 101 on this? How long >> > event data stays present, how long till it's purged? I'm assuming it's >> > a setting you can adjust in the ADF, but haven't looked yet. >> > >> > 3. Should I check the DeviceAddress column in the NSSubscriberDevice >> > view, via my subscription management, to see if an email address >> > already exists before I add it again? I'm trying to plan for if >> > someone registers under accountname1/emailaddress1, and then they come
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 |