26/07/2011 10:02:50 PM
DBAs and DB Developers commonly overlook concurrency when in the "panic" of troubleshooting an urgent performance problem, as they look at CPU, disk or memory bottlenecks. DB Developers commonly override SQL Server's default locking behaviour without understanding the full implication of what they have done, or that there are better solutions. Understanding SQL Server's locking architecture and how best to change it is important to optimise concurrency performance in your database solutions.
In this session Victor Isakov [i](MCA, MCM, MCT, MVP)[/i] will cover the internals of how SQL Server locking works, how you can override the default locking behaviour in SQL Server, and some guidance / best practices around how you should optimize your locking strategy. Along the way Victor will dispell some common myths, and show why NOLOCK is a bad idea.
[b]Speaker[/b]: Victor Isakov (SQL Server Solutions)
Victor Isakov is a Database Architect and Microsoft Certified Trainer who provides consulting and training services to various organizations in the public, private and NGO sectors globally, and been involved in different capacities at various international events and conferences. He has authored a number of books on SQL Server and worked closely with Microsoft to develop the new generation of SQL Server Certification and Microsoft Official Curriculum for both instructor led training (ILT) and e-Learning. He is one of the first IT professionals to get the Microsoft Certified Master and Microsoft Certified Achitect certifications globally.
Venue: Sydney Mechanics' School Arts |
Duration 12:00 - 14:00 |
On: Wednesday, 7 September 2011