Re: Set of Subscription Tables to Restore?
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:
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:
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
> 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
> 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
> that must be backed up and restored to insure all Subscrptions are
> in case of catastrophe.
> So, my question. What is the exact set of tables that must be backed up
> 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