That's bad mkay!


We've all heard that things like nested views, cursors, and under/over-indexed tables are bad...but why? What is the real cost of the badness that abounds in the database world? What's really going on when you run that query against a view of a view of a view. How can you quantify what happens when that cursor ends up running the same simple query thousands of times. And how can indexes really impact the way SQL Server decides to solve your queries. In this session we'll talk about the basics of how to read query plans and use extended events to understand why all these things can be big resource drains on a SQL Server. Good times should be had by all.


  • Kris Hokanson

    3 Recordings

    Kris has been building databases for over 20 years. Since SQL Server 7 he’s been looking for ways to shave a second (or an hour) off any query he comes across. His work experience ranges from small construction firms to fortune 200 Oil & Gas corporations. He has designed and administered everything from 10 MB single user databases to enterprise data warehouses using SQL Server and SSIS to consolidate data from hundreds of disparate ERP systems.

Recorded At:

Recorded on:

May 19, 2018

More Info: