We meet an issue that the undistributed commands is very large and keep increasing.
Here is a background:
DBA stopped the replication to implement a solution to fix the incorrect 'del_cmd' for some articles by using sp_addarticle.
It was stopped no less than 24h, the undistributed commands was very large and keep increasing after starting replication again. While comparing the total count and min/max timestamp from publication and subscription, it looks all of the data should be replicated has already replicated without issue.
Get some tips that maybe a bug exists on such operation from SQL Server 2005 to SQL Server 2008, we restarted distribution agent, and the undistributed commands was cleared.
Since the restarted action was done on Friday, and I see the undistributed commands is queued again on Monday after the weekends. I am confusing that if it is really reflected the undistributed commands now....
How can I know which transactions or commands are being replicated, and what kind of commands are waiting for to be subscriber?
Best Regards, Lisa J