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 »
Latency problems are often caused when series of transactions are trying to move a large batch of commands from the Publisher to the Distributor to the Subscribers. The queries below show overall rows counts and index statistics for commands stored in the Distribution database. Use the results of these queries to look for unexpected high-volume
Read More »
A customer called today about an unexplained slowness in SQL Server 2008 on Windows 2008 R2. All SQL data looked great, no blocking, no obvious IO bottlenecks, just overall slow performance. 976700 An application stops responding, experiences low performance, or experiences high privileged CPU usage if many large I/O operations are performed in Windows 7
Read More »
Microsoft SQL Server has the ability to REPLICATE data changes to Oracle. We see more and more customers migrating to SQL Server, then setting up SQL data Replication to move change SQL data back to a legacy Oracle system until the Oracle server is no longer needed. Our customer got this error after setting up
Read More »
Just wanted to give a heads up about a SQL Replication Distribution Agent Latency problem we observed today. The Distribution Agent to 1 subscriber was only delivering about 500 cmds/sec while other subscribers were getting 4000 cmds/sec. We noticed the Distribution Agent was running under a different PacketSize, made that change, no noticeable improvement. While
Read More »