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 |
|
Analyzer
Posting Yak Master
115 Posts |
 Posted - 2009-04-14 : 08:57:05
|
| Currently checking a string of mirrored production DBs are in full sync.Database Mirroring Monitor and applicable PerMon counters suggest synchronization is working sucessfully. However when I compare key table row counts from principal to the mirrored copy by using a SnapShot view on the mirrored copy, I get 'several' tables with radical different row counts.Where do I begin to indentify why only a few tables are not replicating but the majority are - any idea? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2009-04-14 : 09:57:37
|
A database snapshot is a static view of it, so how "new" is the snapshot?Here's a relevant quote from BOL:quote:
A database snapshot is a read-only, static view of a database (the source database). Multiple snapshots can exist on a source database and always reside on the same server instance as the database. Each database snapshot is transactionally consistent with the source database as of the moment of the snapshot's creation.
Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog"Let's begin with the premise that everything you've done up until this point is wrong." |
 |
|
|
Analyzer
Posting Yak Master
115 Posts |
Posted - 2009-04-14 : 11:01:51
|
| Excellent. As suggested I created a new snapshot which returns a result showing all the tables are in sync when comparing row counts. I knew the mirrored copy was in a constant state of being updated, however over looked the fact snapshots are static after the point of creation. Many thanks for your assistance |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
Mirroring Replica Discrepancy