As mentioned in previous post the @immediate_sync = N’true’ allows you to add a new Transactional Replication subscriber anytime during the Retention Period as both the Snapshot files on disk and the “cached” transactions stored in the distribution database will be available to bring a subscriber up-to-date with the Publisher. One small catch: SQL Distribution
Read More »
The “default” Agent Profile enables “-HistoryVerboseLevel 1” which provides limited detail in the Distribution database history tracking tables. Using Replication Agent Profile “Verbose history agent profile.” enables “-HistoryVerboseLevel 2” which provides additional diagnostic data while troubleshooting SQL Server Replication. The “Verbose history agent profile.” can be set using Replication Monitor for all types of SQL
Read More »
I was recently asked for recommendations for Merge Replication capacity planning project. While I spend most of my time tuning and troubleshooting Replication environments, I decided to post some thoughts on about stress testing and capacity planning. I hope this posting helps as you are designing your Merge Replication environment. Background Reading Merge Replication Performance
Read More »
The Microsoft SQL Server Support team uses various scripts to collect Replication and Performance data from customer’s SQL Servers. These scripts extract data into either text files or into temporary databases which are then backed up and sent to Microsoft SQL Engineer for analysis. Below are links to some of these common data collection scripts.
Read More »
Change Data Capture feature of SQL 2008 is based on Transactional Replication. CDC and Transactional Replication used the same internal stored procedure sp_replcmds to retrieve data updates from the transaction log. However, unlike Transactional Replication, CDC does NOT require the tables to have a unique index (or Primary Key). In fact CDC can be use
Read More »