﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / SQL Server 2008 High Availability  / How can i resolve undistributed commands in Transaction replication / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sat, 25 May 2013 00:41:23 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: How can i resolve undistributed commands in Transaction replication</title><link>http://www.sqlservercentral.com/Forums/Topic1401795-1549-1.aspx</link><description>From the replication monitor as you can see the value for Performance critical, Expiring soon/Expired, and Uninitialized subscription are warnings. When a warning is displayed, the Status column also displays if an agent is running. For example, the status could be Running, Performance critical. So confirm whether you see any value in Status column.I believe the below steps wil answer for your queries..1.I stopped SQL Server Agent on my Distribution server in order to effectively stop all replication jobs (although I probably could have manually stopped each of the individual replication jobs instead).2.I re-ran EXEC dbo.sp_MSdistribution_cleanup @min_distretention = 0, @max_distretention = 1 in order to clean-up the distribution history older than 1 hour.  This outputted that no transactions were removed.3.I re-ran sp_browsereplcmds and saw that I still had a number of transactions in MSrepl_commands.4.I restarted SQL Server Agent which restarted all the replication jobs.5.Magically, the undistributed commands went to zero!6.A quick re-run of sp_browsereplcmds showed that I still had the same number of transactions in MSrepl_commands.  I</description><pubDate>Wed, 02 Jan 2013 07:20:22 GMT</pubDate><dc:creator>KumarSQLDBA</dc:creator></item><item><title>RE: How can i resolve undistributed commands in Transaction replication</title><link>http://www.sqlservercentral.com/Forums/Topic1401795-1549-1.aspx</link><description>These commands need to be apply at subscriber right then how can i restart SQL Server Agent.....Is this resolve this kind off issues.What it mean by undistributed commands. If i restart agent, How to these can be applied to subscribers.In Replication monitor, Status of Subscriptions are showing as Uninitialized subscribers.</description><pubDate>Wed, 02 Jan 2013 06:42:17 GMT</pubDate><dc:creator>Simha24</dc:creator></item><item><title>RE: How can i resolve undistributed commands in Transaction replication</title><link>http://www.sqlservercentral.com/Forums/Topic1401795-1549-1.aspx</link><description>Hi Friend,If the number of undistributed commands was very high and increasing. Go and restart the sql server agent at the distributor, and like magic the undistributed commands was back down to 0 again.</description><pubDate>Wed, 02 Jan 2013 05:54:35 GMT</pubDate><dc:creator>KumarSQLDBA</dc:creator></item><item><title>How can i resolve undistributed commands in Transaction replication</title><link>http://www.sqlservercentral.com/Forums/Topic1401795-1549-1.aspx</link><description>Hi,We are reconfigured publication and subscription but undistributed commands to subscriber is showing very huge No command to be distributed :7777Please find the attachment....Help me how can i resolve this</description><pubDate>Wed, 02 Jan 2013 05:37:10 GMT</pubDate><dc:creator>Simha24</dc:creator></item></channel></rss>