For SQL 2005 and SQL 2008 the sp_removedbreplication stored procedure works great for removing the SQL Replication bits from a database. SQL 2000 has an older version of this SP which doesn’t always cleanup the database. You can use the following steps in SQL 2000 to remove the leftover Replication bits. Problem Description – Manually
Read More »
A customer called today about an unexplained slowness in SQL Server 2008 on Windows 2008 R2. All SQL data looked great, no blocking, no obvious IO bottlenecks, just overall slow performance. 976700 An application stops responding, experiences low performance, or experiences high privileged CPU usage if many large I/O operations are performed in Windows 7
Read More »
Updated post on The process could not execute ‘sp_replcmds’
A customer recently noticed their Published database transaction log would continue to grow until they backed up the Distribution database. DBCC OPENTRAN() Oldest distributed LSN : (0:0:0) Oldest non-distributed LSN : (982:100898:1) --> 0x000003D6 : 00018A22 : 001 -- Commit Tran(sp_replshowcmds) 0x000003D6:00018A22:0004 select [Current LSN],[Operation],[Transaction ID], Left([Description],20) from::fn_dblog('0x000003D6:00018A22:001','0x000003D6:00018A22:0004') “… to clear out the Transaction Log
Read More »
Latency problems are often caused when series of transactions are trying to move a large batch of commands from the Publisher to the Distributor to the Subscribers. The queries below show overall rows counts and index statistics for commands stored in the Distribution database. Use the results of these queries to look for unexpected high-volume
Read More »