Tips for using Merge Replication in SQL Server 2019 (Part 2) Run the Snapshot Agent as infrequently as possible. The Snapshot Agent bulk copies data from the Publisher to the Distributor, which results in some performance degradation. So, try to schedule it during CPU idle time and slow production periods. Specify the -Validate parameter of the Merge Agent. This parameter...
Tag: Snapshot Agent
Tips for using Merge Replication in SQL Server 2019 (Part 1)
Tips for using Merge Replication in SQL Server 2019 (Part 1) Consider setting the -MaxNetworkOptimization parameter of the Snapshot Agent to 1 to avoid sending irrelevant deletes to the Subscriber. Irrelevant deletes are DELETE commands that are sent to Subscribers for rows that do not belong to the Subscriber’s partition. The default value of the -MaxNetworkOptimization is 0. Setting -MaxNetworkOptimization...
Tips for using Snapshot Replication in SQL Server 2019 (Part 2)
Tips for using Snapshot Replication in SQL Server 2019 (Part 2) Consider locating both the publisher and the distributor on the same physical server. You can place the publisher and the distributor on the same physical server when the publisher server can perform the distribution tasks without any performance problems. By the way, using a separate SQL Server for the...
Tips for using Snapshot Replication in SQL Server 2019 (Part 1)
Tips for using Snapshot Replication in SQL Server 2019 (Part 1) Snapshot replication is a simplest type of replication. With this kind of replication, all replicated data (replica) will be copied from the Publisher database to Subscriber/Subscribers database on a periodic basis. Snapshot replication is best used as a method for replicating data that modified infrequently and when the size...
Troubleshooting SQL Server 2017 Merge Replication
Troubleshooting SQL Server 2017 Merge Replication If you have problems with SQL Server 2017 merge replication, review this troubleshooting checklist to find potential solutions. 1. Check that account the SQL Server and SQL Server Agent services runs under belongs to the Administrators local group and is a member of the Domain Users group. The LocalSystem account does not have network...
Tips for using Merge Replication in SQL Server 2017 (Part 2)
Tips for using Merge Replication in SQL Server 2017 (Part 2) If you do not need continuous replication, do not configure the Merge Agent to run continuously. Try to schedule the Merge Agent to run at regular intervals instead of running continuously. Try to schedule it during CPU idle time and slow production periods. By using it, you can decrease...
Tips for using Merge Replication in SQL Server 2017 (Part 1)
Tips for using Merge Replication in SQL Server 2017 (Part 1) Avoid using join filters with five or more tables. Because join filters with five or more tables can significantly degrade merge replication performance, you should avoid join filter for the small lookup tables, or denormalize the database design instead of using join filters with five or more tables. Use...
Tips for using Transactional Replication in SQL Server 2017 (Part 2)
Tips for using Transactional Replication in SQL Server 2017 (Part 2) Consider using transactional replication to memory-optimized tables. In SQL Server 2017, tables acting as transactional replication subscribers, excluding peer-to-peer transactional replication, can be configured as memory-optimized tables. To configure the subscriber database for supporting replication to memory-optimized tables, you should set the @memory_optimized property to true by using sp_addsubscription...
Tips for using Transactional Replication in SQL Server 2017 (Part 1)
Tips for using Transactional Replication in SQL Server 2017 (Part 1) Avoid publishing unnecessary data. Try to restrict the amount of published data. This can results in good performance benefits, because SQL Server will publish only the amount of data required. This can reduce network traffic and boost the overall replication performance. Increase the -MaxBcpThreads parameter of the Distribution Agent....
Tips for using Snapshot Replication in SQL Server 2017
Tips for using Snapshot Replication in SQL Server 2017 Run the Snapshot Agent as infrequently as possible. The Snapshot Agent bulk copies data from the Publisher to the Distributor, which results in some performance degradation. So, try to schedule it during CPU idle time and slow production periods. Consider specifying a simple or bulk-logged recovery model for the subscription database....