Database alterations while Publishing enabled

What are the basic rules for the publisher and subscriber when you wish to
make a database change like adding a column?
- make the change to both databases
- just one and replicate the change
- disable publishing, drop subscriptions before, etc.
Thank you so much ( as I read the current posted subjects),
Bob
Robert,
sp_repladdcolumn and sp_repldropcolumn are the standard way of making schema
changes. Using these procedures, the dependant replication framework (sps,
triggers etc) will be updated as well. Changing existing columns can only be
done in a roundabout way (before SQL 2005). You could add a new column with
the new datatype (sp_repladdcolumn), do an update on the table to populate
the column, then drop the original column (sp_repldropcolumn). Do this again
to create the column having the same original name.
HTH,
Paul Ibison
|||Paul,
After the new columns have been added does the Snapshot have to be run and the subscription reinitialized for the changes to be replicated to the Subscriber? What happens if the subscription is not reinitialised?
Thanks
Chris R
|||Chris,
you only need to synchronize - DON'T ReInitialize whatever you do! -
otherwise a new snapshot will need to be created and then all the articles
will have to go to the subscribers.
HTH,
Paul Ibison