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 »
SQL Replication allows you to replicate user-defined Stored Procedures code to subscribers similar to replicating tables. When the sp is modified, the new schema/script is transferred to the subscriber. This ensures all subscribers have the most recent version of the SP. Transactional Replication also allows you to setup a subscriber using a backup of the
Read More »
As we know, Transactional Replication moves data from the Publisher to the Distributor then to the Subscribers. When working, data flows near real-time through both of these steps. When problems occur which interrupt this flow, latency is introduced. The challenge is to find which step is contributing to the overall latency. Tracer Tokens help you
Read More »
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 »
I was teaching a class this weekend at http://www.sqlsaturday.com/60/eventhome.aspx on using Change Data Capture to pull changed data from SQL Server. I complete my class so I headed over to Thomas LaRock http://thomaslarock.com/ class on WAITS AND QUEUES. It was a great class and I always enjoy listening to Thomas speak. He has a great
Read More »