The following list of tips and tricks will help you enhance replication performance and monitoring.
Keep in mind that transactional replication offers the best performance of all the replication types. Far too often, clients use snapshot or merge replication when transactional replication is the best choice. For instance, you should use snapshot if your data changes infrequently, if a large portion of data changes or if clients don't require an up-to-date data set.
In all other cases, consider transactional replication as only the changes that will go across the wire to your clients. Snapshot will send the entire data set (potentially in gigabytes) each time, whereas transactional could be sending megabytes. The difference will be especially acute if you are replicating over low-bandwidth lines.
Replication tips: Performance
- Replicate tables without primary keys
- Achieve bi-directional replication
- Replicate stored procedure execution
- Create lightweight tables on the subscriber
- Put subscription database in Bulk Logged recovery model
- Use the independent agent option
- Change your polling interval
- Maintain your log
- Set performance profiles
Replication tips: Monitoring
- Check subscriber status with Replication Monitor Group
- Expire subscribers
Replication tips: Miscellaneous
- Replicate to objects with different schemas
- Reveal replication commands
- Check number of commands to be replicated
- Prevent updates, inserts and deletes from being replicated
About the author
Hilary Cotter has been involved in IT for more than 20 years as a Web and database consultant. Microsoft first awarded Cotter the Microsoft SQL Server MVP award in 2001. Cotter received his bachelor of applied science degree in mechanical engineering from the University of Toronto and subsequently studied both economics at the University of Calgary and computer science at UC Berkeley. He is the author of a book on SQL Server transactional replication and is currently working on books on merge replication and Microsoft search technologies.
Tip: Heterogenous data replication using SQL Server