?

Log in

Sigh... - John [entries|archive|friends|userinfo]
John

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Sigh... [May. 18th, 2011|10:09 pm]
John
Some friendly advice. If you have a co-worker who used to be part of Microsoft's SQL support team, don't tell him that a scheduler deadlock is a shortage of available threads (it isn't), and for heaven's sake *do not* tell him that starting a transaction causes locks to be held until the transaction is committed or rolled back.

It's true - starting a transaction *does* keep locks held until the transaction is completed (committed or rolled back), but it's also like telling a person that they should not try to exit their car when it's traveling faster than 60 miles an hour.
linkReply

Comments:
[User Picture]From: suzilem
2011-05-20 12:08 am (UTC)
Oracle used to be worse (I don't know if it still is, I haven't done as much DBAing in the past few years). You can get block locks instead of row locks.
(Reply) (Thread)