Understanding Isolation Levels in Transaction: ASP Alliance

ASP.NET Tutorials » Understanding Isolation Levels in Transaction

Not Logged In. Login

AspAlliance
Register
Edit My Profile
Author List
Write for Us
About AspAlliance
Contact Us
Privacy Policy
Link To Us
Advertise

Subscribe
Free Newsletter
Newsletter Archive
RSS Syndication

.NET Tutorials
Learn .NET
Learn WCF
Learn WPF
Learn ASP.NET
Learn AJAX
Learn Silverlight
Learn Visual Studio
Learn ADO.NET
Learn LINQ
Learn C# (CSharp)
Learn VB.NET
Learn Web Services
Learn Controls
Learn BizTalk
Learn SharePoint
Learn Mobile
Learn SQL
Learn SQL Reporting
Learn Windows Forms
Learn XML
Learn Crystal Reports
Learn FarPoint
Learn DevExpress
Examples
ASP.NET 2.0 Examples

ASP Tutorials
Learn ASP
Learn VBScript
Learn JScript
Learn SQL
Learn XML

Software Resources
Shopping Cart Ecommerce
Charts and Dashboards

Other Resources
Learn Java
Learn Oracle
Opinion / Editorial
Crystal Reports Alliance
WPF Resources
AJAX Resources
Silverlight Resources

Free Tools
Cache Manager
SimpleCMS

Reviews
Book Reviews
Product Reviews
Expert Advice

Books
ASP.NET Developer's Cookbook
Sample Chapters
Book Reviews

Community
Regular Expressions

Print Add To Favorites Email To Friend Rate This Article
Understanding Isolation Levels in Transaction

page 4 of 6

by SANJIT SIL
Feedback

Average Rating:

Views (Total / Last 10 Days): 27127/ 48

Article Contents:

Comparison of Isolation Levels

The isolation levels in the following table are arranged from the least degree of locking to the highest degree of locking. The default, ReadCommitted, is a good compromise for most transactions.

Isolation Level	Dirty Read	Non Repeatable	Phantom Data	Concurrency
ReadUncommitted	Yes	Yes	Yes	Best
ReadCommitted	No	Yes	Yes	Good
RepeatableRead	No	No	Yes	Poor
Serializable	No	No	No	Very Poor

« (Page 3)

View Entire Article

(Page 5) »

User Comments

No comments posted yet.

Community Advice: ASP | SQL | XML | Regular Expressions | Windows