'Is there a definitive list of the MS SQL Server functionality that is incompatible with Transactional Replication

I'm running a SQL Server system (SS2019), which currently uses Merge Replication, and is about to be converted to using Transactional Replication.

I'm (painfully!) aware of many things that are not immediately and seamlessly supported, when Merge Replication is enabled.

  • sp_rename
  • Adding Indexes to tables after creation.
  • (de facto) Using DACPAC for migration mgmt.
  • Modifying huge datasets over capped Network connections 😓

Many of these have work-arounds available, but they fundamentally lead to "you have to work around MergeRepl)

Is there a definitive Source for a list of things that you can't do to the Publisher of a TranRepl database, or that requiring additional work to be replicated to the Subscriber.

i.e. if I just pretended that the new system didn't have TranRepl ... is there a page that tells me what would/could go wrong?

sql-servertransactional-replicationmerge-replication


Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source

Related Questions