UPDATE: 4/10/2020 The steps below walk through setting SQL Server 2016 Replication Publisher, Distributor, and Subscriber each in an Always On Availability Group with one set of replicas residing one 1 subnet and 2nd set on another subnet simulating 2 different data centers (Pub1, Dist1, Sub2) <–> (Pub2, Dist2, Sub2). More Information: Configure replication with
Read More »
Chris Skorlinski, Microsoft SQL Server Escalation Services Customer planning for migration to SQL Server 2016 asked for clarification on running mixed version of SQL Servers in their Replication Topology. I searched for “mixed version”, but was unable to find our posted topic. My colleague George Mason tracked it down under “upgrade”. I’m posting key paragraph
Read More »
LogReader fails with error 15517: 2010-02-25 21:16:35.054 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'CHRISSKACER'.'. 2010-02-25 21:16:35.056 The process could not execute 'sp_replcmds' on 'CHRISSKACER'. 2010-02-25 21:16:35.057 Status: 0, code: 15517, text: 'Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot
Read More »
Sakthivel Chidambaram | Microsoft SQL Server Support There are situations where you initialize a Transactional subscription from a backup and later you need to add an article. If the publication was created using Snapshot Replication, you can re-run the Snapshot Agent and only the newly added article is BCP’ed out then BCP’ed in at the
Read More »
Sateesh Yele Microsoft SQL Server Support Symptom: The Distribution Clean up job fails with the following error. Executed as user: Domainname\Username. Could not remove directory ‘C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\ReplData\unc’. Check the security context of xp_cmdshell and close other processes that may be accessing the directory. [SQLSTATE 42000] (Error 20015). The step failed. Consider the following
Read More »