Replication and log shipping are two features of SQL Server that are used for managing data and ensuring that it is available in multiple locations. Both of these features can be useful for organizations that need to maintain multiple copies of their data in different locations, such as for disaster recovery or to support multiple locations. Replication….. is a process …
Backup Retention Part 1 Backup Retention Part 3 In part 1 I spoke about why you would want to restore from backups and some other reasons to have an older backup around. In part 2 I will dive more into the specific types of backup retention methods. Part 3 I will define more on methods but also cover combined methods …
I have been doing more and more replication work lately, and when recently testing some replication work I needed to create and drop some test databases and re-test the replication work. After configuring a database for replication, then deleting the publisher and the subscriber I attempted to drop the database and get the following error: Msg 3724, Level 16, State …
Cannot drop the database because it is being used for replication Read more »
Working with Transactional Replication with many of our SQL Server clients, one of the big questions that we are always asking is replication keeping up? Recently when deleting a few hundred million rows from a large table that is synced with transactional replication, I needed to programmatically check how the distribution was keeping up. The one measure that indicated that …
When working with SQL Server transactional replication, one of the common checks to see if things look healthy is to insert a tracer token into the replication data stream and see how long it takes to get to the subscribers. This is a process that can be very tedious if you have multiple publications to check, as you need to …
I can remember several years ago every time someone mentioned SQL Server replication you would hear a dull groan. It is one of those things that certainly has some barriers to entry to learn how it works and what you need to do to keep it running. Not me, I get excited about working with replication. I work with several …
The more and more I work with replication the more and more I run into weird errors like this one. SQL Server replication requires the actual server name to make a connection to the server. Specify the actual server name. (Replication.Utilities). You might be thinking to yourself that you had a typo in the server name, but no, after checking …
SQL Server replication requires the actual server name to … Read more »
I have been doing more and more replication work lately, and when recently testing some replication work I needed to create and drop some test databases and re-test the replication work. After configuring a database for replication, then deleting the publisher and the subscriber I attempted to drop the database and get the following error: Msg 3724, Level 16, State …
Cannot drop the database because it is being used for replication. Read more »
This video is a 12 minute demo of how to quickly configure merge replication and to see it in action between SQL Server 2019 and SQL Server 2017. However most of what is included here will work on SQL Server 2005 or newer. Transcription: Steve Stedman 0:02Hi, I’m Steve Stedman, and welcome to this quick demo on merge replication. Merge …
Working on a recent SQL Server merge replication project we needed to update some of the servers in a merge replication scenario without upgrading all of them. Consider a merge replication setup with a publisher, a distributor and 2 or more subscribers all on the same version of SQL Server, and you need to upgrade the SQL Server version on …