SQL Server 2019 Cumulative Update 13 and SQL Server Management Studio 18.10, both out today, combine to offer a neat improvement to peer-to-peer replication. Starting with CU13, there’s a new last-writer-wins option for conflict resolution. When the same data is updated on two different replication servers, whoever saved the data most recently, overwrites everybody else. If you’re a senior database administrator who’s been burned by replication conflicts before, that might sound a little terrifying, but it’s awesome for the right use case strategies.
This only works with peer to peer replication, and it requires a new hidden column that stores the update date in datetime2 format. For more details, check the conflict resolution documentation, which has already been updated to reflect the new option.
Both CU13 and SSMS 18.10 offer other improvements and bug fixes as well, and you can head to their respective pages to see more details.
