|
Hi, Replication is held in week by week in our environment. So may i know what is the steps to be follow after replication.........like DBCC CHECK IDENT... kindly give me the full procedure to follow me.....it is really helpful for all new DBA's Quick reply's are highly appreciated.........
(comments are locked)
|
|
Replication is a mechanism for doing, in general, one of two things, creating a copy of a database that you can then write reports against or query (snapshot isolation for one time use, and transactional replication for near real time copying), or taking data from multiple sources and ensuring that all of them match (merge replication). Once you have replication up and running, it's not like running a restore process. There is no "after" that I'm aware of at all. You will want to set up monitoring to ensure you know how your replication is behaving (assuming you're doing transactional or merge replication), along with all the standard monitoring you should already have in place. Hi Grant Frichey......thank u for your answer.........But my question is what are the steps to be follow in source database after replication.......that is if any issues in replication can we check the identity in the table and is it should be reset identity column in table? ........
Sep 07 '12 at 11:05 AM
askmlx121
I don't understand. Which type of replication are we talking about. For snapshot, there's nothing to do. For transactional replication, you need to monitor the replication process because of the distribution server goes offline, you can fill the log. For merge... cross your fingers & hope everything runs. But there isn't an "after" that I've ever done. So you need to help understand what problem you're trying to solve or prevent.
Sep 07 '12 at 11:08 AM
Grant Fritchey ♦♦
ok thank you........Grant Fritchey........
Sep 07 '12 at 11:21 AM
askmlx121
(comments are locked)
|
