Re: Repeatable read. What is it exactly...
From: Kalen Delaney (replies_at_public_newsgroups.com)
Date: 12/01/04
- Next message: raj: "Does Indexes actually make queries fast?"
- Previous message: Geoff N. Hiten: "Re: What to watch for, when to panic"
- In reply to: Ant: "Repeatable read. What is it exactly..."
- Next in thread: Ant: "Re: Repeatable read. What is it exactly..."
- Reply: Ant: "Re: Repeatable read. What is it exactly..."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 30 Nov 2004 19:45:03 -0800
Repeatable read and serializable are very similar, and your question is far
from stupid.
In repeatable read, SQL Server will hold locks on the data you have read
until the end of the transaction. (Normally, in read committed, locks on
data you have read are released as soon as you are done reading.) So no one
can change change the data until you commit or rollback. Updates and deletes
are not permitted.
Serializable prevents INSERTS of new data that satisfy a condition that you
used for searching.
Example
BEGIN TRAN
SELECT * FROM titles
WHERE price < 5
-- suppose the above returns 2 rows; in repeatable read, those two rows are
now locked and no one can change them
-- until you commit or rollback; but someone in another connection could
insert a whole new row with price < 5
-- So, in serializable you are absolutely guaranteed that if you run the
exact SELECT again, you will get the same result:
SELECT * FROM titles
WHERE price < 5
-- But, in repeatable read, you might get more rows back, because of
inserts.
COMMIT TRAN
In repeatable read, SQL Server locks the data you read.
In serializable, SQL Server locks the data and the 'gaps' between the data.
-- HTH ---------------- Kalen Delaney SQL Server MVP www.SolidQualityLearning.com "Ant" <Ant@discussions.microsoft.com> wrote in message news:78571FC8-E575-4D1C-BA59-E07C2C176A80@microsoft.com... > Sorry for such a basic question but what exactly is a Repeatable read as > far > as transaction Isolation levels go. I understand the concept of > serializable, > read committed & read uncommitted but i can't find any documentation that > describes the repeatable read level. How does this isolation level affect > concurrency. Sorry for such a stoopid question but it woud really help if > I > got the low down once & for all. Many thanks in advance. > Ant
- Next message: raj: "Does Indexes actually make queries fast?"
- Previous message: Geoff N. Hiten: "Re: What to watch for, when to panic"
- In reply to: Ant: "Repeatable read. What is it exactly..."
- Next in thread: Ant: "Re: Repeatable read. What is it exactly..."
- Reply: Ant: "Re: Repeatable read. What is it exactly..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
