PRIMARY KEY violation

Describe your issue

I have a system that creates a lot of “Save” requests to the database. For the procedure, I use the .InsertOrReplace() method, but I get the PK violation a few times an hour. Why is this so? Shouldn’t this method be PK violation safe? Any solutions for this?

Stack trace:
System.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint 'PK_Orders'. Cannot insert duplicate key in object 'dbo.Orders'. The duplicate key value is (52529786).
The statement has been terminated.
   at Commerce.Orders.Infrastructure.Sql.Repositories.Internal.OrderBaseRepository.Save(Order order, Boolean publishDomainEvents)
   at Commerce.Orders.Infrastructure.Sql.Repositories.OrderRepository.Save(Order order, Boolean publishDomainEvents)
   at Commerce.Orders.Infrastructure.Raven.MigrationRepositories.MigrationOrderRepository.Save(Order order, Boolean publishDomainEvents)
Error Number:2627,State:1,Class:14

            db.InsertOrReplace(convertedOrder);

Environment details

Linq To DB version: 4.2.0

Database (with version): SQL Server 2019

ADO.NET Provider (with version): System.Data.SqlClient 4.8.2

.NET Version: .NET framework 4.8

[MaceWindu]

Serializable should help. Another option could be something like that:

db.Table
    .Merge("HOLDLOCK")
    .Using(new[] { record })
    .OnTargetKey()
    .InsertWhenNotMatched()
    .UpdateWhenMatched()
    .Merge();

[KlausBenislavskis]

Serializable should help. Another option could be something like that:

db.Table
    .Merge("HOLDLOCK")
    .Using(new[] { record })
    .OnTargetKey()
    .InsertWhenNotMatched()
    .UpdateWhenMatched()
    .Merge();

Why does merge API operations cost so much more? InsertOrReplace was done in 1-3 ms and the code you sent does it in 45-60 ms