SQL 2005 replication question

[kodaksmile]

I set up transaction replication (sql 2005) on a rather large database. The snapshot was generated successfully based on what I see in replication monitor. I also noticed the log reader does not have any new transaction however when I look in replication monitor under undistributed commands it shows that there are over 6000 transactions to distribute that will take around 10 hours however, this count is not going down. I did check some row counts on several tables between the publisher and subscriber and the counts match. The other odd part is I found when I compared the used space in the data files between the publisher and subscriber (we are replicating all tables via a pull subscription) the subscriber is showing a little over half the used space as the publisher.

1st question - what does the undistributed commands screen really mean?

2nd question - how can I really tell if the subscriber has applied the snapshot successfully?

thanks,

 

[kodaksmile]

Well I think I figured it out - restarting the distribution job seemed to clear the counts though I have no idea why because all the data was replicated.

Strange.....

 

[mrdenny]

1. That is just what it sounds like. A count of the inserts/updates and deletes which have not been sent.

2. Check the agent history. It will tell you if it's sent it over or if it's still processing.

Sounds like your distribution agent got hung for some reason. This can happen sometimes.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog