Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
HammerJeff
Starting Member
1 Post |
 Posted - 2011-11-07 : 08:54:34
|
| Afternoon all.I have three SQL servers (London, Colchester and Wickford) partaking in Merge Replication. One of the servers (Colchester) went down last week and although Replication has restarted, there is data on my London and Wickford databases that should be on the Colchester database. Downtime was not long, but I need to make sure the DBs are in sync. How can I do this?Kind regards |
|
|
garyn
Starting Member
5 Posts |
Posted - 2011-11-08 : 18:13:49
|
| In SQL Server Management Studio, expand the Replication node of the Publisher server; expand Local Publications node. For each publication, right-click and select Validate All Subscriptions. Or from T-SQL, sp_validatemergepublication or sp_validatemergesubscription. BOL has considerable info under "Validating Replicated Data". |
 |
|
|
garyn
Starting Member
5 Posts |
Posted - 2011-11-08 : 18:21:34
|
| BTW, do not assume that all validation errors that are detected, were the result of this downtime. Pushing a snapshot could regress changes made to subscriber schemas, including not only index definitions & freespace changes, but also PK range constraints and identity-seeds (we find manually-controlling our identities across servers works more reliably than the automatic control provided by SQL 2000). So if your snapshots are big (causing intolerable client behavior during a table drop & recreation), or if you are not confident that a snapshot push will be acceptable, you should disable the job called "Reinitialize subscriptions having data validation failures". |
|
|
|
|
|
|
Merge Replication