|File Size||3.72 MB|
|Create Date||September 23, 2017|
Collect a baseline for a SQL Server instance and analyze it against current stats to tell if something abnormal is going on with your SQL Server.
How do you know when your server is on fire? Without a set of known-good measurements to compare against, you don’t. This session will show you how to capture a performance baseline for a SQL Server instance and help you decide what to capture, and where to store it. Finally we will put it all together by walking through a scenario using the captured baseline data to identify a problem.
- Know what to capture for a baseline for a SQL Server instance.
- How to capture a baseline for a SQL Server instance.
- How to analyze current stats against an existing baseline.
She also tinkered with databases in middle school to keep her sports card collection organized.
Tracy has volunteered through the NC Guardian ad Litem program since 2003 advocating for abused and neglected foster children in court.This is her passion outside of SQL Server and favorite job.More information about this program in North Carolina can be found at http://volunteerforgal.org or the national organization CASA at http://www.casaforchildren.org.
Latest posts by Tracy Boggiano (see all)
- Creating a PowerShell Module from a DBA’s Perspective - September 26, 2017
- Automatically Fixing High VLF Count on SQL Server 2012+ - September 19, 2017
- T-SQL Tuesday #94 – Automation Through PowerShell Checking the Status of AGs - September 12, 2017