klaus_aschenbrenner.jpg

Klaus Aschenbrenner

Klaus Aschenbrenner provides SQL Server Consulting services across Europe and the US. He helps people around the world to understand, use, and run SQL Server installations in their environments. In the years 2004 - 2005 Klaus was honored with MVP awards from Microsoft for his tremendous support of the .NET Community. Klaus is also the author of the book Pro SQL Server 2008 Service Broker (ISBN 1590599993) published by Apress in August 2008.
http://www.sqlpassion.at

Service Broker provides several new key features for building SOA applications directly with SQL Server 2005.
SQL Server 2008 provides a lot of scaleout technologies.
Service Broker: Message in a bottle
Do you already wanted to know how SQL Server 2008 stores a database file physically on the hard drive? In this session you will learn the internal structure of a SQL Server 2008 database file.
Service Broker provides several new key features for building SOA applications directly with SQL Server 2008.
Do you know SQL Server Execution Plans? Yes! - and can you read/analyze them? No... For the beginner it is not very easy to understand and explain execution plans generated by SQL Server for your queries.
It's Friday, 05:00pm. You are just receiving an email that informs you that your SQL Server has enormous performance problems! What can you do? How can you identify the problem and resolve it fast?
For the most DBAs and DEVs the TempDb is a crystal ball. But the TempDb is the most critical component in a SQL Server installation and is used by your applications and also internally by SQL Server.
Do you have enough from "normal" performance tuning sessions? You can't hear anything about Indexing and Execution Plans anymore? Then you are right in this session!
Join this session to make a deep dive into how SQL Server implements physical locking with lightweight synchronization objects like Latches and Spinlocks.
Join me in this session to get a basic understanding of Bookmark Lookups, and why they can be dangerous in SQL Server.