It sounds easy at first: just look at the list of fields in the WHERE clause, and put them in the index keys. But what order should you put them in? There’s a common misconception that the most selective (or unique) fields should go first. For example, if you have a column with a million…
1 Designing Indexes for the WHERE Clause
It sounds easy at first: just look at the list of fields in the WHERE clause, and put them in the index keys. But what order should you put them in? There’s a common misconception that the most selective (or unique) fields should go first. For example, if you have a column with a million...
To access this incredible, amazing content, you gotta get Recorded Class Season Pass or Fundamentals of Index Tuning, or log in if you already shelled out the cash.
- 0 Prerequisites Before the Class
- 2 Lab: Indexing for WHERE
- 3 Designing Indexes for ORDER BY
- 4 Lab: Indexing for WHERE + ORDER BY
- 5 Designing Indexes for JOINs
- 6 Lab – Indexing for Joins
- 7 SQL Server’s Built-In Index Recommendations
- 8 Recap and Next Steps
- Bonus Lab – Getting Index Recommendations and Tuning Them