14/10/2014 11:05:42 AM
Are you optimistically reading “dirty” or being seriously pessimistic with serializable? Are your reads really repeatable? Do you have any phantoms in your transactions and how to prevent them from haunting you? Where and how row versioning comes into the picture?
Isolation levels in Microsoft SQL Server offer different ways to define to which extent reads in one transaction must be isolated from the changes done in other, concurrent transactions. Choosing the right isolation level is finding a balance between the required integrity of the data that is being read and consequences that isolated reading has on the other transactions and users.
This session will cover all types of isolation levels in SQL Server through practical and easy-to-understand examples. It will also cover specifics of the snapshot isolation level, its effects on [tempdb] and what needs to be considered before you start using it.
Venue: Sydney Mechanics' School Arts |
Duration 12:00 - 14:00 |
On: Wednesday, 5 November 2014