Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up.
Sign up to join this community
I read here and here that, when connecting to a Sql Server read-only replica, the isolation level used is ALWAYS SNAPSHOT. It says it ignores SET TRANSACTION ISOLATION LEVEL statement and any locking hints.
Is this true?
Is it also true for Azure SQL Database replicas?
What happens if the snapshot isolation level is disabled?
when connecting to a Sql Server read-only replica, the isolation level used is ALWAYS SNAPSHOT. It says it ignores SET TRANSACTION ISOLATION LEVEL statement and any locking hints. Is this true?
Microsoft documentation says the same, see Benefits section of link below:
Is it also true for Azure Sql Database replicas ?
On both SQL Server and Azure SQL Database, when you connect to readable secondary, transaction isolation level will be Snapshot
What happens if the snapshot isolation level is disabled?
Even if you disable ALLOW_SNAPSHOT_ISOLATION or READ_COMMITTED_SNAPSHOT on database on primary replica, sessions on secondary will still use Snapshot mode because row versioning will still be used internally
