If I want to add a new table to an existing subscription, I use the commands:
- create the repdef for the new table
- mark the table for replication using sp_setreptable
- create article for the new table specifying an existing publication
- validate publication
- create subscription with the "for new articles" option (really should be called "alter subscription", whatever). Also, I'll be using the "without materialization" option here.
- run "check subscription"
My question is, is it ok to run all these commands on a live system where other tables in the publication/subscription have data changes replicating? Or should I quiesce data changes on the other tables first?
When running sp_setreptable, do I need to stop the rep_agent before running this command? (it doesn't say to do this in the manuals, but historically, we've been doing it at my site)
Thanks in advance
Ben