Here is a quick ReplTip on difference in SQL Management Studio and Replication Monitor for Push v. Pull Subscriptions. Push v. Pull with Management Studio For PULL subscribers you must connect via SSMS or Remote Desktop (RDP) connection to the Subscriber to performance administrative tasks like starting, stopping, or changing parameters. The icon changes to
Read More »
SQL Server 2012 supports Managed Service Account (MSA) is a special type of domain account assigned to a single computer used to manage a service like SQL Server, but no passwords to remember! SQL Server 2014+ support group Managed Service Account (gMSA) provides the same functionality within the domain but also extends that functionality over
Read More »
ecently I posted Repltalk a walkthrough setting up Publisher, Distributor, and Subscriber each in AlwaysOn Availability groups. In this series of postings, I’m going to break then, show you what went wrong, and how to fix it. Let’s start with error message when attempting to validate a redirected publisher. [crayon-651708879ef47933428712/] Msg 21892, Level 16, State
Read More »
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 »
Problem Setting up Transactional Replication in an AlwaysOn Availability Group environment and getting error similar to one shown below: Msg 14262, Level 16, State 1, Procedure sp_MSrepl_track_addjob, Line 57 [Batch Start Line 12] The specified table (‘MSrepl_agent_jobs’) does not exist. MSrepl_agent_jobs is a new table added to Distribution database in SQL 2017 CU6 and SQL
Read More »