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 »
While helping a customer on a Replication issue, we encountered an very unusual error message. An error occurred during decryption. There is no remote user 'distributor_admin' mapped to local user '(null)' from the remote server 'repl_distributor'. Changed database context to 'master'. (Microsoft SQL Server, Error: 15466) There are some key words in this error (‘distributor_admin’,
Read More »
José Moreira Neto Microsoft Escalation Engineer I ran into an issue where the customer was complaining that Merge Replication was generating “fake” conflicts. This customer has a straight SQL Server Merge Replication with no filters where the only non-default setting is the use of the Microsoft Maximum Conflict Resolver a very specialized feature in Merge
Read More »
Yes you can use both Transactional and Merge Replication to move data inserted using the BCP.exe utility of the Bulk Insert command to Subscribers. Considerations For Transactional Replication By default, Transactional Replication will replicate data loaded via BCP or Bulk Insert. For performance, you may want to load data using the bcp Utility –b batch_size
Read More »
I was teaching a class this weekend at http://www.sqlsaturday.com/60/eventhome.aspx on using Change Data Capture to pull changed data from SQL Server. I complete my class so I headed over to Thomas LaRock http://thomaslarock.com/ class on WAITS AND QUEUES. It was a great class and I always enjoy listening to Thomas speak. He has a great
Read More »