November 21, 2014 at 8:22 am
Hi,
What is the 'put back' procedure after I run
sp_removedbreplication
for my database?
I'm new at replication, set up a snapshot puclication with a pull subscription. In order to add column to a table in the publisher I used the
sp_removedbreplication. There are so many 'parts' with the simple set up I've done; jobs etc. I'm not sure how to get it working again after making the schema change.
What I'd like is a
sp_putbackdbreplication
Does something of the sort exist?
John
SQL 2012 Standard VPS Windows 2012 Server Standard
December 4, 2014 at 12:16 pm
Hi Johnny,
I'm not a replication expert, but I don't think there is a function like that. Typically when I have a need to drop and put back replication I script out the Publisher or Subscriber stuff or take screen shots of all the settings and recreate the replication after it's removed.
Also, in the case of adding a column or table I believe you don't need to drop and re-add replication. When I have something new at the publisher, I right click it and click properties. In the properties there is a option called "Articles" where you can add/remove new tables/columns etc.
Hope that helps a little
December 4, 2014 at 12:51 pm
When you create a publication, there is an option to replicate schema changes which will propagate changes to the subscription automatically.
But not always! If you add a column, as an example, it must be added to the end of the table.
Changing an existing column will break replication.
This is snapshot replication, script out the publications, subscriptions, and drop and re-create them whenever the underlying schema changes.
There is no need to completely remove replication.
Transactional replication is a different story, however.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply