Eric Lucht | Microsoft SQL Server Escalation Services Logging Options When the Merge subsystem is initialized, agent logging is automatically enabled using default values. The Agent will begin logging in the replmerg.log being created in the 100\COM (90\COM for SQL 2005) folder. This blog posting covers registry keys used to override the logging level of
Read More »
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 »
Amit Banerjee | Microsoft SQL Server Support TSQL Code: MS_MergeAgentStatistics.sql script located on SkyDrive MergePerformance or TechNet Code Share I have sometimes found the need to track the performance of the Merge Agents configured on the server without having to dig through the Replication Monitor or through the Merge Agent job history outputs. So, here
Read More »
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 »
Rishi Maini | Microsoft SQL Server Escalation Services All about “Not for Replication” “Not for Replication” is a property which can be set for different objects like Check constraints, Foreign Key constraints, Triggers , Identity columns etc while using SQL Server Replication. Feature used when the DBA would like the transactions to behave differently when
Read More »