You use Activity Monitor to figure out what’s going on, and you feel like you might be missing something.
“Is something going on with the SQL Server right now?” You hear those words, and your heart starts to race a little faster. You try to connect to the SQL Server, and it responds, but you can tell it’s a little slow. You open up Activity Monitor, look at recent expensive queries, and maybe open up the Windows event logs to see if anything’s happened recently.
There’s gotta be a better way, right?
Good news – there is, and you’re about to learn how the pros do it. In one all-demo session, you’ll watch Brent Ozar use sp_WhoIsActive, sp_BlitzFirst, and sp_BlitzCache to solve several common emergencies. You’ll walk away with a written checklist to solve typical performance emergencies.
Why I Want to Present This Session:
I want to bring more disciplined troubleshooting processes to our industry.
Latest posts by Brent Ozar (see all)
- What to Do When SQL Server is Unusually Slow - February 25, 2018
- Getting Better Query Plans by Improving SQL’s Estimates - February 25, 2018
- How Often Should You Run Backups and CHECKDB? - February 25, 2018