[DB] From Locks to No Locks – Concurrency in SQL Server


In this session we take a look at essential mechanisms inside SQL Server, which influence administrators as well as developers and should be known thoroughly.
Why does SQL Server have to lock objects, which effects does this have (performance and data integrity) and how we can influence these things.
Specifically we will look at:
· Can indexes prevent locking?
· Why is NOLOCK not a good idea when dealing with critical data?
· When and what happens at Lock-Escalation?
· What does table-design have to do with blocking?
· Why everyone should know error number 1205 – how deadlocks can occur and what can prevent them?
· How is „optimistic concurrency“ implemented in SQL Server?
. How does In-Memory OLTP change the game?
As usual: lots of (code) demos

Speaker: Andreas Wolter (MVP, MCM, MCSM)
Andreas Wolter has been specialized in SQL Server for 18 years. He is not only a Microsoft Certified Master (MCM) but also one of 2 Microsoft Certified Solutions Masters Data Platform (MCSM) in the Asia Pacific Region and has been awarded with the MVP several times.
His company Sarpedon Quality Lab, which offers its services in Europe, the Middle East, Southeast Asia, and Australia is focusing on development and optimization of high performing OLTP Systems and big Data Warehouse Architectures.