User guide
3. Use the second drop-down list to select Top SQL Source. You should now see the Top SQL
Source Settings that are being applied Globally.
4. Change the Minimum Duration to the desired value, it will be saved automatically.
If you wanted to configure the Top SQL Minimum Duration Collection Setting for an individual
Connection:
1. Select the desired Connection node in the Navigator pane.
2. In the Settings pane, use the drop-down list to select Top SQL Source. You should now see
the Top SQL Source Settings that are being applied for that Connection.
3. Change the Inherit From Parent Setting to False.
4. Change the Minimum Duration to the desired value, it will be saved automatically.
ADJUSTING GLOBAL RUNTIME THRESHOLD SETTINGS
By default, the global Runtime Threshold Settings for SQL Server Agent jobs are set at a Minimum
Runtime Threshold Percent of 10% and Maximum Runtime Threshold Percent of 250%. This
means that anytime a job runs for less than 10% of its average runtime or longer than 250% of its
average runtime you will be notified. If you find you are receiving too many notifications, these
settings can be adjusted. See example below:
If you wanted to configure the SQL Server Agent Job Maximum Runtime Threshold Percent
globally:
1. Select the Shared Groups node in the Navigator Pane
2. In the Settings pane, use the top drop-down list and select SQL Server Settings.
3. Use the second drop-down list to select SQL Server Agent Job. You should now see the SQL
Server Agent Job Settings that are configured globally.
4. Change the Maximum and Minimum Runtime Threshold Percents to the desired values.
You can also specify explicit time-based thresholds here. Time-based thresholds are usually less
valuable at the global level, particularly the Minimum Runtime Threshold which doesn't have much
value at all globally. Explicit time-based thresholds tend to be more applicable at the actual connection
or object level for overriding the global percentage thresholds on a case-by-case basis.
Note: Anytime an explicit time-based threshold is specified it will override the percentage based
thresholds for that object.
For example, consider a job that has a great deal of volatility in runtime such as a transaction log
backup, and can run for anywhere between 30 seconds and 30 minutes, with an average runtime of 5
minutes. To avoid unnecessary percentage-based threshold notifications for the job, you might want
to set its Maximum Runtime Threshold to "35 Minutes" and Minimum Runtime Threshold to "20
Seconds". This can be done by selecting either the job's node in the Navigator or an instance of the
SQL Sentry Quick Start 25
©2015 SQL Sentry. All Rights Reserved.