We noticed a large published database was taking a long time for the Snapshot to be applied to the subscriber. Looking further in sp_who and sys.sysprocesses we noticed only one Distribution Agent thread executing the bulk insert statements. It took a while but we discovered the publication was created using “concurrent snapshot” option. -MaxBcpThreads number_of_threads
Read More »
Replicate Execution of Stored Procedure and CDC: With Transactional Replication you can replicatethe execution of the Stored Procedure like this: This has several advantages as discussed in this article: http://msdn.microsoft.com/en-us/library/ms152754.aspx . When you enable Change Data Capture (CDC) at the Database level, replication of the stored procedure execution will NOT work. This is By Design.
Read More »
ReplTalk ReplTip – Replication Agent fails with “unable to start correctly” Taiyeb Zakir Microsoft SQL Server Escalation Services When you have a large number of SQL Server Agent or Replication Agent Jobs running, some of the Jobs may not even start. You might see an error like this in the Event log: “The application was
Read More »
In Transactional Replication Subscriber reinitialization instructs the Distribution Agent to locate and distribute a NEW Snapshot to the Subscriber. In Merge Replication, the reinitialization is done by the Merge Agent. Depending on the Replication settings, the Subscriber tables may either be 1) dropped, deleted, or 3) truncated resulting in loss of data on the Subscriber.
Read More »
by Chris Skorlinski, Microsoft SQL Server Escalation Services Oracle Publishing, now deprecated in SQL Server 2014, provides ability to use Oracle server as a Transactional Replication Publisher to a Microsoft SQL Server subscriber. Oracle Publishing Overview http://technet.microsoft.com/en-us/library/ms151229.aspx This feature was as designed as an Oracle to Microsoft SQL Server migration tool. Other customers used Oracle
Read More »