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 |
|
augustinius
Starting Member
1 Post |
 Posted - 2008-04-07 : 14:07:25
|
| I was pointed to this forum by one of the admins who has started doing some consulting work for us. We did a major conversion over the weekend for our main production server to SQL 2005 from SQL 2000. We have used replication to go from the live OLTP server to a few dedicated report servers for all of our reporting needs. In 2000 this was pretty well established (though a pain when we had to migrate in changes; I love the 2005 schema features for replication).The only problem we have really encountered today, the Day After, involves replication. A few minor things involve lack of knowledge (like nonclustered indexes don't replicate by default, that was an OOPS). But one thing I haven't figured out yet.Replication is working -- we are updating three servers, and all three servers are getting updates. I have run a validation on one of them and it passed in full. However, the "undistributed commands" count never goes down. It actually keeps going up and up. I verified that by first running this on the subscriber: select transaction_timestamp from MSreplication_subscriptions And taking the results of one of the three rows that came back and executing this with it: sp_browsereplcmds @xact_seqno_start = '0x00000231000006ED000100000001' which brought back all of the "undistributed commands". Within that list, I looked for sp_MSins_ procedures. I found a few and looked up on the subscriber the value to be inserted -- and it existed on the subscriber. So it still is in MSrepl_commands even though it has been sent out. I am afraid that eventually the system will "think" that the process isn't working and deactivate the subscriptions. Also this is useless as a monitor. Since this is our first major replication in 2005, I am willing to bet that we are missing something. Does anyone have any advice? |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-04-07 : 23:58:09
|
| Like on sql2k, sql2k5 has job to clean up distribution db. Sql may keep replicated commands up to 12 hours, depends on how you set snapshot. For UC index, there is option to copy them. Default is not copy. |
 |
|
|
|
|
|
Undistributed Commands not decrementing