September 14, 2004 at 2:09 pm
Hello Everyone,
with Yukon beta 1 we must add the trace flag 3970 to use the new snapshot isolation level.
With Yukon beta 2 the server does not seem to work with this trace flag. And snapshot isolation level does not seem to work by default...
Anyone aware of this?
Thank's a lot,
Carl
September 15, 2004 at 6:19 am
Hi Carl,
The trace flag is not a requirement now. BTW, what transaction Isolation mode are you working on? It seems to work for me flawlessly with the database compatibility level of 90.
Vinod Kumar (MVP-SQL Server)
September 15, 2004 at 9:20 am
Hello Vinod,
Here is what I try to do:
alter
database test_carl SET READ_COMMITTED_SNAPSHOT ON
SET
TRANSACTION ISOLATION LEVEL SNAPSHOT;
begin
transaction
select
* from booking where booking_id = 5
Result:
Msg 3952, Level 16, State 1, Line 1
Transaction failed in database 'test_carl' because the database does not allow snapshot isolation. Use ALTER DATABASE to allow snapshot isolation.
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
If I try this:
alter database test_carl SET READ_COMMITTED_SNAPSHOT ON
begin
transaction
select
* from booking where booking_id = 5
Same error.
Maybe I am doing something wrong?
Thank's
Carl
September 15, 2004 at 9:24 am
Also: My database compatibilty level is 90 and I want to use the READ_COMMITTED_SNAPSHOT isolation level with row versioning.
Carl
September 15, 2004 at 10:01 am
Ok I found my error... Here is the correct order to use row versioning with read committed isolation level:
alter
database test_carl SET READ_COMMITTED_SNAPSHOT ON
SET
TRANSACTION ISOLATION LEVEL READ COMMITTED ;
begin
transaction
select
* from booking where booking_id = 5
...
Best regards,
Carl
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply