August 9, 2006 at 12:42 am
| i am responsible for replicating data for 45 databases for servers in different regions. Sometimes i need to do the restore process on one of the databases. i tried several ways to do this but none gave me the right solution. i need any help on the steps that i should do before restoring, and i have some questions. what sql replicating services should i stop? should the backup be a full or differential or it doesn't matter? should the restore be full or differential or it doesn't matter? is there a way? Thank u for your help!! |
August 9, 2006 at 1:38 am
Joseph
More information needed, please. What type of replication are you using, and in what topology? What database are you trying to restore (publication, disribution, subscription)? Are you restoring from a backup of the very same database or from a database on a different server? Will the restore be a regular task or just required on an ad hoc basis?
John
August 16, 2006 at 5:21 am
i am using continous replication. i am trying to restore publication database. i am restoring from database on other server. the restore is not a regular task.
August 16, 2006 at 5:21 am
i am using continous replication. i am trying to restore publication database. i am restoring from database on other server. the restore is not a regular task.
August 16, 2006 at 9:45 am
I noticed after I posted my reply that you're on SQL 2005, so I may not be the best person to help. However, if replication on 2005 is anything like 2000, you should be able to restore the publication database. Bear in mind that any differences between the "old" and "new" databases will not be replicated to the subscriber. Also, be careful if any of your tables have identity columns - be sure to read about this so you understand the implications. I would stop all replication agents before restoring, but in particular the logreader agent.
Good luck
John
August 17, 2006 at 12:17 am
i am using sql 2000
i stopped all the agents including the log reader. then i restored the publication database using differential restore. after the restore:
- the database is no longer marked by a small hand.
- a publisher is no more seen
- the subscriber is still seen on the replication monitor
- i can't delete the subscriber(i am reported by sql error)
- i had to cleen this shit by removing the records manually by deleting records from the distribution database
August 18, 2006 at 2:21 am
Not sure what you mean by "differential restore". Perhaps you need to set up replication again. I've never had to do this before. Have you checked the Microsoft website to see whether there are any papers on restoring publication databases? It shouldn't be too difficult just to recreate the publication and the articles in it... especially if you already had them scripted.
John
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply