- Replication needs should be clearly defined before creating a replication topology. Successful replication can be difficult and requires much pre-planning.
- Ideally, publishers, distributors, and subscribers should be on separate physical hardware.
- Create, document, and test a backup and restore strategy. Restoring replicated databases can be complex and requires much planning and practice.
- Script the replication topology as part of your disaster recovery plan so you can easily recreate your replication topology if needed.
- Use default replication settings, unless you can ensure that a non-default setting will actually improve replication performance or other issues. Be sure that you test all changes to ensure that they are as effective as you expect.
- Fully understand the implications of adding or dropping articles, changing publication properties, and changing schema on published databases, before making any of these changes.
- Periodically, validate data between publishers and subscribers.
- Regularly monitor replication processes and jobs to ensure they are working.
- Regularly monitor replication performance, and performance tune as necessary.
- Add alerts to all replication jobs so you are notified of any job failures.
Hi, Self Introduction: I am Vang chew bigger , currently I am working with Citronics , Here my role is SQL Server Database Administrator , I am having 3+ yrs Exp in SQL SERVER DBA with T-SQL, I have experience on SQL Server 2000, 2005 and 2008, I have a great experience on installation and configuration of SQL SERVER versions, and also applying the patches, hot fix, services packs and RTM’s accordingly, involved in upgrading on in place and side by side as per client requirement, and also Migrating the database on SQL SERVER 2000 to 2005 and 2008, Solid experience on configuring and maintenance of High availability SQL Server solutions, including Log shipping, Database Mirroring, Replication(Transactional and Merge) and SQL Server Clustering., having experience on performance tuning on server level, database level and query level, Responsible for working with application developers in identifying,...
Comments