February 1, 2019 at 6:52 am
I've read that on https://docs.microsoft.com/en-us/sql/t-sql/queries/hints-transact-sql-table?view=sql-server-2017
PAGLOCK
Takes page locks either where individual locks are ordinarily taken on rows or keys, or where a single table lock is ordinarily taken. By default, uses the lock mode appropriate for the operation. When specified in transactions operating at the SNAPSHOT isolation level, page locks are not taken unless PAGLOCK is combined with other table hints that require locks, such as UPDLOCK and HOLDLOCK.
Does the option "Is Read Commited Snapshot On" is concerned by this or it is just the "Allow Snapshot Isolation"?
February 6, 2019 at 3:31 pm
mbichari - Friday, February 1, 2019 6:52 AMI've read that on https://docs.microsoft.com/en-us/sql/t-sql/queries/hints-transact-sql-table?view=sql-server-2017PAGLOCK
Takes page locks either where individual locks are ordinarily taken on rows or keys, or where a single table lock is ordinarily taken. By default, uses the lock mode appropriate for the operation. When specified in transactions operating at the SNAPSHOT isolation level, page locks are not taken unless PAGLOCK is combined with other table hints that require locks, such as UPDLOCK and HOLDLOCK.Does the option "Is Read Commited Snapshot On" is concerned by this or it is just the "Allow Snapshot Isolation"?
Just snapshot isolation - it's not the same thing as Read Committed snapshot.
If it matters, the differences are listed in the Row Versioning Isolation table under the SQL Server Database Engine Isolation Levels section in the following documentation:
Transaction Locking and Row Versioning Guide
Sue
February 7, 2019 at 5:32 am
Thanks for your reply =)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply