Microsoft SQL Server Indexing Index Internals performance tuning SQL Server DBA T-SQL
Marble Falls, Texas, United States
Former rocket scientist and USAF Fighter Pilot -- now a SQL Server geek (24 years)! Past opportunities include free-lance technical writer for PC Magazine, Senior Software Manager for government sponsored munitions effectiveness committee, and insurance company CTO. Currently senior database engineer consultant for several Austin companies.
Presenter at 17 SQL Sat sessions in 2016, 10 in 2017, 8 in 2018 (Cambridge) and Chicago, Jacksonville, Dallas, Pensacola, Austin, and Baton Rouge in 2019; as well as several local SQL Server user's groups in Ft. Worth, Austin, and San Antonio; and 2 Virtual DBA presentations in 2018.
Specialize in SQL Server tuning and T-SQL instruction.
In former times Rocket Scientist, USAF Fighter/Test Pilot, IT Director for Tactical Missile Studies, IT Director at Texas Windstorm Insurance Association, and now working as an independent consultant specializing in SQL Server performance tuning and T-SQL instruction.
You’ll find a lot of Word of Mouth (WOM) advice out there about SQL Server performance, especially
when it comes to indexes. Some of the things you have probably heard are:
keep clustered index width small
unique indexes perform better
keep non-clustered index width small
compressed indexes have fewer logical reads
add one index for each column
But how do you know if this advice is good or bad? Did you know that there is a way to look under the hood at the actual index pages to see how the data is stored, and how it’s stored differently when data is compressed? Using this information, you can prove or disprove the WOM advice.
Attend this demo-heavy session to learn how the SQL Server optimizer uses indexes. It’s all about
performance, and the right indexes will give your application a big performance advantage.