Tips for using Transactional Replication in SQL Server 2019 (Part 2) Consider increasing the -CommitBatchThreshold parameter of the Distribution Agent. This parameter specifies the number of replication commands to be issued to the Subscriber before a COMMIT statement is issued. The default value is 1000. If you do not need continuous replication, avoid configure the Distribution Agent to run continuously....
Tag: replication
Tips for using Transactional Replication in SQL Server 2019 (Part 1)
Tips for using Transactional Replication in SQL Server 2019 (Part 1) Try to keep transactions as short as possible. Because SQL Server send changes from the Publisher to Subscriber as INSERT, UPDATE, and DELETE statements you should keep transactions as short as possible to help the Distribution Agent to transfer transactions through the network. By the way, keeping transactions as...
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 Transactional Replication
Troubleshooting SQL Server 2017 Transactional Replication If you have problems with SQL Server 2017 transactional replication, review this troubleshooting checklist to find potential solutions. 1. Check that you have sysadmin permissions on the SQL Server. Only members of the sysadmin server role can configure replication, so if you have not these permissions you cannot setting up or configure transactional replication....
Troubleshooting SQL Server 2017 Snapshot Replication
Troubleshooting SQL Server 2017 Snapshot Replication If you have problems with SQL Server 2017 snapshot replication, review this troubleshooting checklist to find potential solutions. 1. Check that you have sysadmin permissions on the SQL Server. Only members of the sysadmin server role can configure replication, so if you have not these permissions you cannot setting up or configure snapshot replication....
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....
Troubleshooting SQL Server 2016 Transactional Replication
Troubleshooting SQL Server 2016 Transactional Replication If you have problems with SQL Server 2016 transactional replication, review this troubleshooting checklist to find potential solutions. 1. Install the latest SQL Server 2016 service pack. Because some SQL Server 2016 Transactional replication bugs were fixed in SQL Server service packs, you should install the latest SQL Server service pack. At the time...
Tips for using Very Large Databases in SQL Server 2016
Tips for using Very Large Databases in SQL Server 2016 Try to create as many database files, as there are physical disk arrays so that you have one file per disk array. This will improve performance, because when a table is accessed sequentially, a separate thread is created for each file on each disk array in order to read the...
Some tips for using Merge Replication in SQL Server 2016 (Part 2)
Some tips for using Merge Replication in SQL Server 2016 (Part 2) 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. Set the “Maximize Throughput for Network Applications” […]