Interview Speaker
summary
Developer mistakes cause most slow queries: over-fetching columns (using SELECT ), doing heavy joins when only first and last name are needed, and skipping tests and paging. A one-day SQL Server performance tuning workshop and a live SQL Server 2019 on Docker demonstration show 2017 vs 2019 side-by-side and practical fixes. Advice: treat NoSQL cautiously—try in staging not production—and prefer selecting only the rows and columns actually used.
AI-written summary · about
related talks
52mWriting T-SQL code for the engine, not for you "more demos" by popular demand- 52mWriting T-SQL code for the engine, not for you "more demos" by popular demand
02h 42mSQL (The Return): Demystifying Preconceptions and Using the DB Effectively- 52mWriting T-SQL code for the engine, not for you "more demos" by popular demand
58mTroubleshooting CPU Performance Issue for SQL Developers
05mAfter analyzing 600,000 SQL queries, these are the top mistakes developers make
49mPerformance Features in SQL Server and Azure SQL
01h 00m50 Things All SQL Server Developers Need to Know