Ever had a database change go horribly wrong? It can feel awful in the moment, then eat away at your confidence for days afterward. In this 20 minute episode Kendra gives you practical steps that help you cope with change over the course of your DBA career.
An important query is suddenly slow. Is it because statistics are out of date? This is tricky to figure out, and updating statistics right away can make troubleshooting even harder. Learn how to use query execution plans to get to the heart of the question and find out if stats are really your problem, or if it's something else. In this 35 minute episode:
00:39 SQL Server 2017 Announced
01:10 New video from Microsoft's Joe Sack demonstrating Adaptive Query Processing
03:05 This week's question: Are bad stats making my query slow?
05:26 Demo of finding plan in cache and analyzing stats begins
28:17 What to do when stats ARE the problem
Code samples: https://gist.github.com/LitKnd/f07848d59cedc61fd057d12ab966f703
Links from the episode:
SQL Server 2017 Adaptive Query Processing video by Joe Sack: https://www.youtube.com/watch?v=szTmo6rTUjM&feature=youtu.be
Michael J Swart on finding Dark Matter Queries: http://michaeljswart.com/2017/04/finding-your-dark-queries/
Got a question for Dear SQL DBA? https://SQLWorkbooks.com/ask
They made their index maintenance job smarter, and their queries got slower in production afterward. Could the index maintenance have harmed performance? In this episode...
00:50 Thinking about plan freezing in Query Store and multi-team process
03:15 This week's question about index maintenance and query performance
The dev server got bogged down during a deployment and lock timeouts were everywhere. Was the perfmon counter way off about how much memory was being used just for locks? In this episode...
00:33 What's new @ SQL Workbooks: Down the Rabbit Hole
03:00 This week's question about lock timeouts & memory in SQL Server