Recently worked on a case where customer was getting this error when modifing the Distribution agent Job to use CommitBatchSize of 12K and above: Agent message code 20028. An invalid parameter or value was specified in the command line. (parameter = ‘-commitbatchsize’, value = ‘12000’) This error occurs when setting commitbatchsize greater than 10000. The
Read More »
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 »
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 »
Jared Poché, MCSE, MCDBASQL Server Sr. Support Escalation EngineerProduct Support Services (PSS) – Charlotte, NC — updated 2/24/2019 One of the advantages of replication is that subscribing servers can be used for reporting thereby offloading RO query activity from the Publisher. Recently I worked on a performance case on such a replication subscriber, which would
Read More »
SQL Server Transaction LogReader Agent timeout executing sp_replcmds occurs most often when a large transaction(s) are written to the Published database transaction log, or 100s of millions of un-replicated commands from logged index maintenance or changes to replicated tables. Either problem requires the LogReader to read more log entries than the timeout parameter allows causing
Read More »