ReplTalk
All about Microsoft SQL Replication

Category: Troubleshooting

New Disaster Recovery option for Peer-2-Peer (P2P) Replication in SQL 2008

Chris Skorlinski [MSFT] Inside Replication, Troubleshooting August 11, 2010

Share this PostProblem: Following a severe systems/replication failure, SQL 2005 requires database updates to be frozen until the peer is re-established. Peer-to-Peer Transactional Replication http://msdn.microsoft.com/en-us/library/ms151196(SQL.90).aspx Maintenance Considerations The following actions require the system to be quiesced (stopping activity on published tables at all nodes and ensuring that each node has received all changes from all
Read More »

Snapshot Files deleted when “@immediate_sync = N’true'” and “@retention = 0”.

Chris Skorlinski [MSFT] Inside Replication, Troubleshooting July 14, 2010

Share this PostAs 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:
Read More »

Using “Verbose history agent profile.” while troubleshooting Replication

Chris Skorlinski [MSFT] Best Practices, Troubleshooting July 13, 2010

Share this PostThe “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
Read More »