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

Re: Set of Subscription Tables to Restore?

Subject: Re: Set of Subscription Tables to Restore?
From: "Andy"
Date: Thu, 1 Sep 2005 08:12:24 -0400
Newsgroups: microsoft.public.sqlserver.notificationsvcs
I was really saying copy the data do another database on the server, not 
another table :).

"Andy" <[email protected]> wrote in message 
news:[email protected]
> What I have done is to copy the data into another table.
>
> The tables that you would be concerned with should be:
>
> <Instance><App> DB tables would be:
> NS<Sub Class>Subscription
> NOTE: when a schema change is made it will copy the existing table to a 
> table called NS<Sub Class>SubscriptionOld, if you are just performing an 
> update to your application. If you have made more than one change to 
> schema, you must rename or drop the table NS<Sub Class>SubscriptionOld or 
> else the update will not be able to be applied, it gives you an error 
> saying the table already exists.
>
> <Instance>NSMain DB tables would be:
> NSSubscribers
> NSSubscriberDevices
>
> Subscribers and devices should not be affected by schema changes to a 
> subscription class, only if you delete the instance and recreate it.
>
> I have not been using NS for very long, but what I have explained is my 
> experience with the product so far. Hope this is helpful.
>
>
> "MarkSW" <[email protected]> wrote in message 
> news:[email protected]
>> I've read Shyam's book and the section on updates possibly failing (p. 
>> 576
>> on).  It mentions two subscription tables that must be restored if a
>> subscription schema changes.  And that you should in general backup the 
>> NS
>> DB's before any schema-changing update.  But the restore instructions on 
>> p.
>> 582 are for restoring the *entire* DB's from the backup instances, which,
>> after an update, will then lose the update.  And I don't see a complete
>> accounting of all tables that hold stateful Subscriber and Subscription 
>> data
>> that must be backed up and restored to insure all Subscrptions are 
>> preserved
>> in case of catastrophe.
>>
>> So, my question. What is the exact set of tables that must be backed up 
>> and
>> retored to guarantee this?
>>
>> My preferred deployment scenario:
>> - Back up all necessary Subscriber/Subscription tables
>> - deploy updated ADF with new schemas
>> - nscontrol update
>> - Restore all necessary Subscriber/Subscription tables
>>
>>
>
> 



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