Today someone asked me how to “roll their own” SQL Replication Monitor to keep an eye on the health of SQL Server Replication. You’ve seen from my previous post I usually use a TracerToken job to monitor SQL Transactional Replication and query against MSmerge_sessions table for Merge Replication. However, you can also create your own
Read More »
SQL Server 2008/R2 Audit Triggers for Change Data Capture changes_tables table — — FILENAME: CDCchange_tablesAudit.SQL — — AUTHOR: Chris Skorlinski — — DESCRIPTION: SQL Server 2008/R2 Audit Triggers for Change Data Capture changes_tables table. — This script is used to audit the activity in the changes_tables table created when — you enable Change Data Capture
Read More »
Have you noticed the SQL Server Agent Job RETRY is set to 2147? Well it is not, the dialog window just cuts off the rest of the digits. Actually the Replication Agent are set by default to retry 2147483647 times, once every minute. That is over 4000 years! 2147483647 = 35791394 Hours = 1491308 Days
Read More »
We encountered an interesting problem the other day I thought I would post on ReplTalk. Customer call when they noticed the SQL Server Agent resources in their SQL 2008 clustered installation would not start. The following error appeared in the Windows Application and System Event log. Windows Application Event Log SQLServerAgent could not be started
Read More »
By default the SQL Replication Agent History cleanup job runs every 10 minutes and deletes any historical data older the 48 hours. If you’re only running SQL Server Replication Agent a few times each day, you can reduce the frequency of this cleanup job and increase the retention period for historical data without impacting SQL
Read More »