Replying the above line resulted in

"504 Gateway Time-out

The server didn't respond in time. "

Altough the reply is already registered in SSC.

Except for replying, is there something else we should pay attention to?

For your deadlock graph to be usable, you need to remove:

<event name="xml_deadlock_report" package="sqlserver" timestamp="2025-03-04T15:16:17.973Z">
  <data name="xml_report">
    <value>
Keep the rest
Remove the bottom
  ...

Tools like Solarwinds SQL Sentry PlanExplorer (free) can help you analyse this situation !

It helps you narrow down the 2 tables that are to be addressed to solve the...

your deadlock graph xml is incomplete !

 

Did you register the SPN up front ? ( We always do, because we do not rely on dynamic port numbers for an instance )

If not:

• If you rely on...

Testing a bit more, it turns out, once you add a clustered MSDTC resource and remove it, it start throwing this error when running "Begin Distributed Transaction"

Even putting back...

The example is not correct !

I copied your scripts to my SQL2019 CU31 and executed them.

This is the result I get:

March 3, 2025 at 8:52 am

#4549840

DBCC clonedatabase does not support Ledger !

ref: https://learn.microsoft.com/en-us/sql/relational-databases/security/ledger/ledger-limits?view=sql-server-ver16#ledger-table-considerations-and-limitations

it was worth a try ....

 

After I notified the devs yesterday, the article states V17, they are going to test that today.

 

FWIW: We re-installed the OS and rebuilt the cluster.

Now it works as it should

 

indeed.

Those settings have been activated.

DTC service has been stopped and started and is on network service

Still Begin distributed transaction fails

Strong suggestion, don't store the images in the database. Can you? Yes. VARBINARY(MAX) would be the way to go. However, it really negatively impacts a whole slew of...

because it has to validate each and every row of the RLS object before it is to be processed by your query