José Moreira Neto | Microsoft SQL Server Escalation Services Problem 1: batch updates 1) A single update command can generate a transaction with thousands of commands. For example if you execute an UPDATE statement that updates 10K rows on the publisher, up to 20K commands can be send over to the subscriber. On the publisher
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 “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 »
Content provided with help of Jonathan Clark, Microsoft SQL Server Escalation Services Oracle to SQL Server replication is used to support customers migrating Oracle legacy application to Microsoft SQL Server. The data changes in Oracle can be replicated near real-time to a SQL Server database. Here is a little background information on the Oracle to
Read More »
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 »