Are the queries to pull data from the Merge Subscribe taking longer then when executed on the Publisher? Looks like it is time to review the index structure for these tables. We encountered an unusual problem in SQL 2005/2008 where the indexes didn’t get created on the Subscriber when the Snapshot was pushed by the
Read More »
Sometimes MS SQL Replication developers use similar names for similar meaning but which can have very different results. These settings both specify alternate location for the Snapshot files, however, one is set at the publication and one at an individual subscriber. alt_snapshot_folder The alt_snapshot_folder parameter is set at the Publisher for ALL subscribers. This can
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 »
Provided by: Suresh B. Kandoth, SR Escalation Engineer, Microsoft SQL Escalation Services These 2 scripts are used by the SQL Server Replication Support team to help analyze the Filter Logic used in Merge Replication. The first lists all defined Subset and Join filters. The first listing shows published table with indexes, the second listing shows
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 »