The Baseline Configuration tab of the Monitored SQL Server Properties window allows you to configure your server baseline options. SQLdm calculates a baseline out of a pool of collected data based on the selected period and collection interval, and is represented by mean, standard deviation, minimum, maximum, and count statistics. One benefit of using this feature is that SQLdm uses the baseline to provide alert recommendations which you can use to set effective alert thresholds.
SQLdm allows you to select the date range used to calculate the performance baseline for one or more selected SQL Server instances. The day and time period fields allow you to select the days and times on which to base your alert baseline calculations. When your SQL Server instances are not busy, clear the days and times to remove them from the calculation and provide a more realistic and accurate baseline. The days and hours selected apply to both the Automatic and Custom baseline selections.
User accounts that include the View privilege can access the Baseline Configuration window, but cannot make any changes. User accounts that include the Modify privilege can make changes to the baseline configuration of their monitored SQL Server instances. |
Access the Baseline Configuration tab
You can access the Baseline Configuration tab of the Monitor SQL Server Properties window by right-clicking the appropriate monitored SQL Server instance, and then selecting Configure Baseline.
Select a baseline period
The baseline period you specify should represent a typical operation of the monitored SQL Server instances to which this baseline applies.
Automatic
Automatic calculates a dynamic baseline based on a moving window of the past seven days of collected data.
Custom
Custom allows you to set a specific time range that does not change.
Apply this baseline to more than one instance
You can apply a specific baseline to additional instances not included when you originally created the baseline configuration.
To add a baseline configuration to additional instances:
- In the Servers pane, right-click the name of any instance that you want to have the new baseline configuration, and then select Configure Baseline.
- Make any necessary changes to the baseline configuration, and then click Apply Baseline Configuration.
- Select the appropriate instances from the Available Servers list, and then click Add > to move them to the Added Servers list.
- Click OK. SQLdm applies this configuration to the other instances.
When verifying your baseline configuration changes for more than one instance in the Change Log view, note that instance property changes are logged only once. In comparison, baseline configuration changes are logged as many times as the number of instances affected by the change. |
Metrics used in baseline calculations
SQLdm uses the following metrics when calculating a baseline for a monitored SQL Server instance:
- Available Memory
- Batches Per Second
- Blocked Sessions
- Buffer Cache Hit Ratio
- Buffer Cache Size
- Checkpoint Writes Per Second
- Client Computers
- Data File Count
- Data File Space Allocated
- Data File Space Used
- Data File Space Used (Percent)
- Database Count
- Disk Queue Length
- Disk Time (Percent)
- Distribution Latency
- Host CPU Usage
- Host CPU Usage MHz
- Host Disk Device Latency
- Host Disk Kernel Latency
- Host Disk Queue Latency
- Host Disk Read
- Host Disk Total Latency
- Host Disk Usage
- Host Disk Write
- Host Memory Swap In Rate
- Host Memory Swap Out Rate
- Host Memory Active
- Host Memory Ballooned
- Host Memory Consumed
- Host Memory Granted
- Host Memory Usage
- Host Net Received
- Host Net Transmitted
- Host Net Usage
- Full Scans Per Second
- Lazy Writer Writes Per Second
- Lock Waits Per Second
- Log File Count
- Log File Space Allocated
- Log File Space Used
- Log File Space Used (Percent)
- Log Flushes Per Second
- Logins Per Second
- Oldest Open Transaction (Minutes)
- Open Transactions
- OS CPU Privileged Activity
- OS CPU User Time
- OS Memory Used (Percent)
- OS Total Processor Activity
- Packet Errors Per Second
- Packets Received Per Second
- Packets Sent Per Second
- Page Life Expectancy
- Page Lookups Per Second
- Page Reads Per Second
- Page Splits Per Second
- Page Writes Per Second
- Pages Per Second
- Physical Memory
- Procedure Cache Hit Ratio
- Procedure Cache Size
- Processor Queue Length
- Read Ahead Pages Per Second
- Replication Latency (Seconds)
- Replication Subscribed
- Response Time
- SQL Compilations Per Second
- SQL CPU Activity
- SQL Memory Allocated
- SQL Memory Used
- SQL Recompilations Per Second
- System Processes
- System Processes Consuming CPU
- Table Lock Escalations
- Tempdb GAM Wait Time Milliseconds
- Tempdb PFS Wait Time Milliseconds
- Tempdb SGAM Wait Time Milliseconds
- Tempdb Size
- Tempdb Size Percent
- Undistributed Transactions
- Unsubscribed Transactions
- Used Memory (Percent)
- User Connections (Percent)
- User Processes
- User Processes Consuming CPU
- Version Store Generation
- Version Store Size
- VM CPU Ready
- VM CPU Swap Wait
- VM CPU Usage
- VM CPU Usage MHz
- VM Disk Read
- VM Disk Usage
- VM Disk Write
- VM Memory Active
- VM Memory Ballooned
- VM Memory Consumed
- VM memory Granted
- VM Memory Swap In Wait
- VM Memory Swap Out Rate
- VM Memory Swapped
- VM Memory Usage
- VM Net Received
- VM Net Transmitted
- VM Net Usage
- Workfiles Created Per Second
- Worktables Created Per Second
SQL Diagnostic Manager identifies and resolves SQL Server performance problems before they happen. Learn more > >