Replication on Andy M Mallon - AM²

snapshot replication - corrupted BCP files

Thu, 18 Aug 2022 22:56:09 -0400

Question

Each night my SQLServer replication failed on a big table with the following error. It is failing on a different table each night but always on a relatively big table ( > 200,000 rows)

The process could not bulk copy into table '"dbo"."Table01"'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20037)
Get help: http://help/MSSQL_REPL20037
Field size too large
Batch send failed
Violation of PRIMARY KEY constraint 'PK_Table01'. Cannot insert duplicate key in object 'dbo.Table01'. The duplicate key value is (0). (Source: MSSQLServer, Error number: 2627)
Get help: http://help/2627
Failed to send batch after max errors (Source: MSSQLServer, Error number: 3621)
Get help: http://help/3621

Can I use both Log Shipping and Transaction Replication at the same time?

Fri, 15 Oct 2021 11:36:11 -0400

Question

Good Morning, I have a SQL Server 2016 that is doing Log Shipping to a DR Site. I currently want to also to Replicate (Transactional) specific Tables to another Server for Reporting Purposes.

Will there be any issues or snafu’s I should be aware of? Can I have Log Shipping and Transactional Replication configured on the same Publishing Database?

SQL Server replication additional subscriber

Wed, 15 Sep 2021 08:48:16 -0400

Question

I have a publisher with the distributor on the same server which is transactional replication. There is also an active subscriber using push method.

I need to set a new subscriber up going to a different server using the same articles as the current subscriber I have. The database is huge and cannot be taken offline so I was going to do an initialize from backup instead of a new snapshot.

Replication of only updates and inserts

Wed, 14 Oct 2020 16:01:08 -0400

Question

I have two sql servers, in the first I want to keep the data from the last three months and in the second I want to keep all the data with the purpose of getting historical reports. I know how to do a transactional replica but I don't know how to replicate only the inserts and updates, I don't want to replicate the deletions.

Replication latency when an Availability Group replica is offline

Mon, 04 May 2020 10:02:52 -0400

Assume you have configured a transactional replication publisher, which is part of an availability group (AG). Now, you have an asynchronous secondary AG (or mirroring) replica that is offline. Perhaps this is a DR node, and you are doing patching or other planned maintenance on that DR node, with it intentionally offline.

Configuring the distribution database in an Availability Group

Mon, 08 Apr 2019 08:00:23 -0400

I 💜 Replication

Starting with SQL Server 2017 CU6 and SQL Server 2016 SP2-CU3, you can now configure your distribution database as part of an Availability Group (AG). Up until now, your distribution database could only be part of a standalone instance, or failover cluster instance (FCI). In this first round, there’s a pretty big list of limitations & restrictions. In fact, you’ll notice that the “supported scenarios” list is shorter than the “limitations or exclusions.”

How to pause the subscriber end of transactional replication

Tue, 12 Feb 2019 08:10:04 -0500

Question

How do I go about pausing transactional replication on the subscriber end.

We have a publisher on Server A, a distributor on Server B and a subscriber on Server C. All are in the same network.

Some background, we have quite a busy BizTalk server where we replicate the data from the BAM parts to a separate database server which will be used for a customized web application for statistics, searching etc. Seeing as the tables in the BizTalk server are both quite large and missing indexes etc since they're basically just there to have data dumped into them we opted to have the second, replicated database in which we can apply various optimizations for reading the data.

how azure sql geo replication works internally?

Fri, 02 Nov 2018 10:22:13 -0400

Question

My company moved to azure and started to use azure Sql database and geo replication.

For our on-premise servers, we heavily rely on Microsoft transactional replication to move data. Now we setup transactional replication between on-premise server (publisher) and azure sql db. Then we found that the transactional replication itself is constantly consuming 100% DTU on azure(we are using a 125 DTU P1).

How can I permanently remove replication by script if I only have access to the subscriber?

Tue, 23 Oct 2018 23:10:17 -0400

Question

We've been building a replication network of DBs to give us some degree of Always On without paying the full price tag. Currently we have a publisher DB which replicates to a handful of subscribers, so that if the publisher goes down, we can promote a subscriber to be the new publisher. As is, this is a tedious manual process, but we want to start scripting elements of it so that the process is quicker and closer to being automated.

Configuring Replication with Availability Groups

Fri, 23 Feb 2018 10:00:41 -0500

I fancy myself more of a Jedi, but I appreciate the Empire's dedication to replication

I’ve used replication and Availability Groups together before. Replication works great with an AG as both a publisher or a subscriber (though, not as a distributor–you can’t add the distribution database to an AG). I was surprised when I recently ran into a problem configuring replication on a database that was in an AG.

Transaction Replication on AlwaysOn

Mon, 17 Apr 2017 22:21:43 -0400

Question

In our AlwayOn environment I have two SQL servers 2014 Ent.edition (SERVER A, and SERVER B). I setup a transaction replication for [database A ], pointing to listener which shouldn't cause any issue if a failover happened. Tested, worked just fine after a failover, but when I shut off one of the servers in AOAG ,in test environment, replication stops working. There is no error on the replication monitor. For testing purpose,I have inserted few records on the database it works fine on AOAG, but on the Subscriber the data modification is not replicated until I bring up the other server. Once the server is up, then the replication start to work. I'm pretty sure, I might be missing something, this can't be this way by design.

Podcast: Mirroring, Availability Groups, Replication, and Log shipping

Wed, 31 Aug 2016 09:29:03 -0400

Have you ever wondered what the best option is for making your data available in your environment? I was asked by Carlos L Chacon (blog|twitter) to be part of a panel on his podcast for an episode discussing some of the options–availability groups, mirroring, log shipping, and replication. We cover each topic in detail and explain the positives and negatives of each one.

Moving Replication to a new server (without re-snapshotting)

Tue, 08 Jul 2014 19:57:00 -0400

Background

The guy in this picture is a Snapshot Agent

At work, we make very extensive use of transactional replication. We have dozens of publications. Most publications have two or three subscribers. We replicate across domains, across subnets, across geographies. We use both push & pull replication (we’ve found pull works best when crossing the globe).