February 22, 2007 at 8:16 am
Does anyone know the limitations of publisher and subscriber databases.
can Publisher and Subsciber be refreshed?
your input greatly appreciated -
Regards!
February 26, 2007 at 8:00 am
This was removed by the editor as SPAM
February 26, 2007 at 6:44 pm
You may need to broaden the scope of your question.
Which replication mechanism are you referring to?
For a brief summary
Snapshot - the whole subscriber gets overwritten manually/automatically (scheduled), no updates go back to the publisher
Merge - updates go back and forth between the subscriber and the publisher manually/automatically (scheduled). Both databases are kept up to date
Transactional - updates go back and forth between the subscriber and the publisher as they happen. Both databases are kept up to date
February 27, 2007 at 11:23 am
Thanks Steve for your repsonse, I'm referring to Transactional replication. I know the publisher and subscriber will be in synch, but I just wanted to know if the databases in question can be refreshed/restored if need be. Do I have to disable replication for this? Thanks
February 27, 2007 at 12:23 pm
Found this in BOL (SQL 2005)
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/repref9/html/d0637fc4-27cc-4046-98ea-dc86b7a3bd75.htm
Might be helpful in explaining how the restore of a subscription database will work.
February 27, 2007 at 11:26 pm
You may need to reinitialized snaphot after restore...
You need stop your replication before restore otherwise you may get the error database in use...
MohammedU
Microsoft SQL Server MVP
February 28, 2007 at 5:31 am
Restoring can be done, but getting replication back in sync is a lot of work. Far easier - if possible within time constraints - is to just plan on doing a new snapshot if you have to restore publisher or distribution databases.
February 28, 2007 at 8:48 am
This answers my question, thanks everyone -
much appreciated!!!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply