This error occurs because of the Transaction Isolation Level.
By default, SQL Compare uses the Serializable Transaction Isolation Level, however this deployment requires a Transaction Isolation Level of Read Committed.
This documentation goes into more detail:
1
1
Was this article helpful?
1 out of 1 found this helpful
Articles in this section
- The operation could not be performed because OLE DB provider ... for linked server ... was unable to begin a distributed transaction (SQL Compare)
- Docker Cannot connect to SQL Server Browser
- How to create a filter for command line comparisons
- SQL Compare Error: The Login is from an Untrusted Domain
- Error: Exiting since no license was found
- "No text is available" in SQL view
- Performance issues with SQL Data Compare
- Why comparison behaviour is different between the GUI and command line?
- Server Aliases not working when connecting with SQL Compare/SQL Data Compare