How to Think Like SQL Server
- Instructor(s): Brent Ozar
- Length: 90 minutes
- Cost: $29
You’re a developer or a DBA, and you’re comfortable writing queries to get the data you need. You’re much less comfortable trying to design the right indexes for your database server. In this series of videos with Brent Ozar, you’ll learn how the SQL Server engine looks at your indexes and builds your query results. Buy it now for $29!
“In the first 30 minutes, your videos were able to accomplish what I have tried for 1 year to get my team to understand. Your videos are well worth the money!” – Anthony S., ISV Team Lead, about our How to Think Like the SQL Server Engine course
In 90 minutes of videos, you’ll learn:
- The differences between clustered and nonclustered indexes
- How (and when) to make a covering index
- The basics of execution plans
- What determines sargability
- What SQL Server uses to estimate the memory your query needs
- What happens when those estimates are wrong
- When you should get fresh estimates by recompiling the query
- How to avoid SQL Server’s public toilet, TempDB
- And it’s all demoed with these Stack Overflow database pages (PDF)
For $29, you get 18 months of access to the videos for one person. You can watch it for 18 months on your desktop, laptop, iPad, or iPhone. Buy it now and get started!
- Length: 7 hours
- Cost: $299
- How to use powerful scripts to identify which queries are killing your server
- What parts of the database server are holding you back
- How to tackle indexing improvements
- How to identify query anti-patterns.
- Length: 6.5 hours
- Cost: $299
- How to create, analyze, and understand clustered and nonclustered indexes
- When to use index includes, filtered indexes, and other special structures to speed up your queries.
- How to use free tools to find hidden columns in your indexes
- How to tune a workload using the SQL Server Dynamic Management Views
- How to avoid common indexing anti-patterns that drag down your database server
- How to find critical index changes in the Execution Plan Cache
- How you can use data to prove that your changes improved performance