row vs page locking...
From: Randall Sell (randall_at_bytewise.nospam.com.au)
Date: 09/05/04
- Next message: John: "Re: Single user mode after maint plan"
- Previous message: Nigel Rivett: "RE: Single user mode after maint plan"
- Next in thread: John: "Re: row vs page locking..."
- Reply: John: "Re: row vs page locking..."
- Reply: Dan Guzman: "Re: row vs page locking..."
- Reply: Kalen Delaney: "Re: row vs page locking..."
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 05 Sep 2004 13:19:48 GMT
Hello all,
Somewhere on these newsgroups I recall reading that SQL Server 6 and prior
(when they were married with Sybase) used page locking and not row level
locking. Hence you could be locking a lot more records then what you think
when doing an UPDATE or INSERT SQL.
Now I notice that SQL Server 7 and 2000 claim to use row level locking. (As
you can see, I have been out of the SQL arena for some time). So what I'd
like to know if this is all true? Or marketing mumbo-jumbo? Has Microsoft
made changes at the core of their engine to lock rows? I know that other
RDMSs like Interbase have a versioning engine so it was built from the
ground up for concurrence. And I've read that MSs row level locking is a
band-aid on its unchanged core engine, although the author of that message
did not expand further on this.
so I figured I'd ask the experts what the truth is. Any help is much
appreciated.
If indeed it has changed, what sort of test can I run to prove this to my boss?
regards,
-randall sell
- Next message: John: "Re: Single user mode after maint plan"
- Previous message: Nigel Rivett: "RE: Single user mode after maint plan"
- Next in thread: John: "Re: row vs page locking..."
- Reply: John: "Re: row vs page locking..."
- Reply: Dan Guzman: "Re: row vs page locking..."
- Reply: Kalen Delaney: "Re: row vs page locking..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|