SUPERCHARGING SQL QUERY PERFORMANCE: UNLEASH THE POWER WITHIN!
summary
Merchant, MerchantProduct and AdvertiserProduct tables on SQL Server grow from ~2M to 24M rows and cause timeouts; adding a composite index (merchant_id, source_product_id) changes a query plan from an index scan reading 3,024 rows to an index seek returning 1 row. Using a temp table typed as varchar vs nvarchar forces a scan (reads jump from 4 to 24) because of type mismatch. Creating an index view for advertiser counts reduces work from scanning 3,024 rows to reading 12 indexed entries.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:34Optimize SQL query performance
- 6:33SQL query execution basics
- 11:36Query execution plans
- 14:30Optimization case studies
- 19:29Index views for aggregation
- 21:18Summary
related talks
53mWhen to stop tuning a query
49mIt’s Not Always About the Index: The Hidden Secrets of Query Performance
07mIndeksimi dhe përmirësimi i performancës në SQL
46mSupercharge Your SQL with Indexes: a Practical Introduction
51mDealing with Very Large Tables in SQL Server- 53mWhen to stop tuning a query
- 51mDealing with Very Large Tables in SQL Server
- 51mDealing with Very Large Tables in SQL Server