"Why Missing-Index Recommendations Mislead"

1. What is the main flaw of the missing-index recommendations provided by SQL Server?

They provide an accurate account of existing indexes on the table. They suggest creating indexes without considering existing ones. They always recommend the best index based on query performance. They only show the total count of existing indexes.

2. When generating a missing-index recommendation, how does SQL Server handle column order?

It arranges columns by their selectivity for optimization. It arranges columns in the order they appear in the table. It prioritizes the columns based on their usage frequency. It only considers the equality columns for ordering.

3. What is a crucial step before implementing any missing-index recommendations?

Reading the recommendations individually without aggregation. Checking for existing indexes on the table. Ignoring the impact percentage of recommendations. Acting immediately on the top recommendation without analysis.

4. What should you do if you find multiple indexes with the same leading key column on a table?

Drop them all immediately. Ignore them as they are not important. Confirm with full inventory and usage stats before deciding. Assume they are duplicates and keep only one.

Continue: "Filtered Indexes for Reporting" → Review this lesson Retake quiz