I’ve not seen this problem for year, but it came up again today. We were following the steps to setup a Merge subscriber using Backup\Restore from the Publisher. The database was very large, no filtering, two subscribers, each with complete match set of data from the publisher. Backup\Restore works great, saves time pushing down individual
Read More »
With SQL Server Management Studio 17.7 release, Replication + Always On technology was fully supported allowing registration\connections via Always On Listeners. This update fully supported use of Tracer Tokens following failover to a secondary Replica. https://docs.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-2017#download-ssms-177 What’s new Replication Monitor: Replication monitor now supports registering a listener for scenarios where publisher database and/or distributor database
Read More »
Stored procedure sp_setsubscriptionxactseqno allows Distribution Agent to skip transaction(s) in Transactional Replication. Internally this stored procedure sets the last delivered watermark (LSN) stored in subscriber’s MSreplication_subscriptions table. Upon restarting the Distribution Agent return transactions greater that this watermark (LSN) from the Distribution database cache (msrepl_commands). [crayon-651701a63fa12228800874/] Skipping Errors Skipping Errors is useful when Distribution Agent is
Read More »
When running manual SQL 2014 SP3 Change Tracking sp_flush_commit_table_on_demand you observe change_tracking_hardened_cleanup_version is not moving forward and syscommittab table not being cleaned up even though auto-clean is enabled. Executing: sp_flush_commit_table_on_demand 1000 The value returned by change_tracking_hardened_cleanup_version() is 1133436. The value returned by safe_cleanup_version() is 1850878. Executing: sp_flush_commit_table_on_demand 1000 The
Read More »
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 »