SQL Server Concurrency Paperback – 11 Sep 2012
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Frequently Bought Together
Customers Who Bought This Item Also Bought
Enter your mobile number below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
Getting the download link through email is temporarily not available. Please check back later.
To get the free app, enter your mobile phone number.
Most Helpful Customer Reviews on Amazon.com (beta)
The only sentence I would perhaps disagree with is on page 180: "SQL Server was designed and built, initially, to use pessimistic concurrency. Therefore we should consider using that model unless we can verify that optimistic concurrency will work better for our application." I think this may not encourage people enough to try RCSI . We switched to Read Committed Snapshot Isolation in 2007 for all our databases and it has worked wonderfully. We even set the is_read_committed_snapshot_on bit in the model database so that every new database gets created and runs in the RCSI isolation model.
Sometimes even one sentence in the book is worth reading the whole book cover to cover. In my case it was "Warning: The NOLOCK hint and RCSI . If application code invokes READ UNCOMMITTED isolation by using the NOLOCK hint ( or the equivalent READUNCOMMITTED hint), changing the database to RCSI will have no effect. The NOLOCK hint will override the database setting, and SQL will continue to read the uncommitted (dirty) data." I turns out we still had some 10 places where NOLOCK was still being used - leftovers from the days before RCSI was implemented.
Her examples and explanations are straightforward and easy for the DBA at any level to follow and understand.
Kalen makes the inner workings of SQL server easy to understand.
Reading this book will make any DBA sound like an expert.