I recently needed to move a Transactional Replicated table to a new File Group. There are a couple of documented Schema changes that can break Replication. http://msdn.microsoft.com/en-us/library/ms151870(SQL.90).aspx However, I found most problems are solved if I first ensure all data between all peers/subscribers is synched, “no replicated transactions”, before making schema change, then sync the
Read More »
Error Number: -1073548784 Executing the query “UPDATE STATISTICS [dbo].[***********] WITH FULLSCAN ” failed with the following error: “Could not allocate space for object ‘dbo.SORT temporary run storage: 142101814116352’ in database ‘tempdb’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup,
Read More »
From time to time we need to restore a customer’s Distribution database to a secondary server or to a lab server for testing. When you restore a distribution database it will not be configured to execute Replication commands such as sp_browsereplcmds. However, there is a simple solution. You can execute the command below to configure
Read More »
Working with a customer to setup a large subscriber we noticed the Merge Agent was NOT doing a BULK INSERT, but instead was doing row-by-row insert. This had significant overhead for the Merge Agent resulting in longer then expected initial/reinit synchronization times. Downloaded 33 change(s) in 'Customer' (33 inserts): 33 total Applied the snapshot and
Read More »
When Replication the EXECUTION of a stored procedure to a subscriber select the “serialized transaction” and and wrap the SP execution within a transactions. This ensures the changes are replicated as a single stored procedure execution and not as individual row-level updates. See: Publishing Stored Procedure Execution in Transactional Replication “The serializable option is recommended
Read More »