Monday, December 16, 2013, 6:00 PM to 8:30 PM
Have you ever executed a T-SQL program that crashed due to an integrity error? Upon inspecting the job history, the error code states you have duplicate key values. However; re-running the job does not reproduce the error. You probably had an transaction isolation level issue without knowing it.
I will be covering the following topics in this presentation.
1 – Maintaining the ACID quality of transactions.
2 – How SQL Server implements transaction durability?
3 – System versus User transactions
4 – Transaction basics
5 – Exploring the various transaction modes
6 – Exclusive versus Shared locks
7 – Blocking versus Deadlocks
8 – How to detect them with my free code.
9 – How Isolation levels affect transaction behavior.
10 – What is a dirty read versus a phantom read?
At the end of the talk, you will know how to fix the above scenario by changing the isolation level.
I have twenty years of data processing and proven project management experience, specializing in the banking, health care, and government areas. My architecture expertise encompasses all phases of the project life cycle, including design, development, implementation, and maintenance of systems.
My credentials include a Masters degree in Computer Science from the University of Rhode Island with concentrations in database technologies and programming languages. I also have Microsoft Certificates for Database Administration (MCDBA) and System Admistration (MCSA).
John is currently a Senior SQL Developer in charge of Data Acquisition and Total Quality Management reporting for Sensata Technologies – Mechanization systems department. The underlying systems use the SQL Server 2008 R2 and Oracle 11i for housing data. When he is not busy informing the members of current events at a local PASS chapter, he spends time with his wife and daughter enjoying outdoor activities.