Enable CDC fails with error Msg 22830, Level 16, State 1, Procedure sp_cdc_enable_db_internal

Chris Skorlinski [MSFT] Troubleshooting January 3, 2011

Problem While enabling Change Data Capture (CDC) on database you get following error: EXECUTE sys.sp_cdc_enable_db Msg 22830, Level 16, State 1, Procedure sys.sp_cdc_enable_db_internal, Line 198 [Batch Start Line 8] Could not update the metadata that indicates database AdventureWorks2012 is enabled for Change Data Capture. The failure occurred when executing the command 'SetCDCTracked(Value = 1)'. The
Read More »

Tips to improve performance when applying Snapshot in Transactional Replication

Chris Skorlinski [MSFT] Best Practices, Troubleshooting March 7, 2010

1) MaxBCPThreads (contributed by Sanjaya Padhi, Microsoft SQL Server Support) I found we can add in the below point to increase the perf of the snapshot application by the distribution agent by use of MaxBCPThreads parameter as mentioned in the article below. Please note this does not apply when Snapshot created using default “concurrent” option.
Read More »

SQL Server Merge Replication Best Practices

Chris Skorlinski [MSFT] Best Practices, Troubleshooting February 2, 2010

I’m posting a collection of SQL Server 2008 Merge Replication Best Practices. The material below includes text from SQL Books Online, other white papers, KB articles, web postings, and little from experience I gained working with SQL Replication for almost 15 years. The “best practices” below are in no particular order. My objective was to
Read More »

SQL Replication Agent will RETRY for 4085 Years

Chris Skorlinski [MSFT] ReplTalk Blog August 25, 2010

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 »

Reducing Impact of Large Updates on Merge Replication

ReplTalk Best Practices April 24, 2011

One key parameter to consider when performing batch updates against tables enabled for Merge Replication is ‘generation_leveling_threshold’. This setting controls how many data changes should be grouped into one generations (or batch). The Merge Agent then collect and sends those batches of changes based on the Merge Agent [-DownloadGenerationsPerBatch] parameter. The default is to group
Read More »