A query in the current transaction cannot read data modified by another transaction that has not yet committed, thus preventing
dirty reads. However, data can still be modified by other transactions between issuing statements within the current transaction,
so nonrepeatable reads and phantom reads are still possible. The isolation level uses shared locking or row versioning to prevent
dirty reads, depending on whether theREAD_COMMITTED_SNAPSHOT database option is enabled. Read Committed is the
default isolation level for all SQL Server databases.
Submitted questions and answers are subject to review and editing, and may or may not be selected for posting, at the sole discretion of w3Sniff.
Get Started
Comments
Leave a Comment