The "sqlserver" probe generates alarms if the query times out or a profile fails to execute in the scheduled time interval.
- Any sqlserver probe
- UIM any version
- sqlserver configuration (sqlserver_monitor.cfg)
Listed below is a complete explanation describing all of the sqlserver profile timeout fields in sqlserver profiles which can help eliminate any timeout alarms/query timeouts/failures:
1. Heartbeat - Defines the interval at which all profile checkpoint schedules will be tested and trigger eventual checkpoint execution.
2. Check Interval - Default value for check interval in the profile.
3. Profile Timeout - Defines the maximum processing time for all checkpoints in the profile.
4. SQL Timeout - Every checkpoint query runs asynchronously.
5. Delay Threshold -
If you are getting alarms for
"Profile <Database Server>, failed to execute in the scheduled time interval, delayed by <seconds> seconds", it means that your profile is taking more time to get executed then the described heartbeat interval.
For example, if the profile is configured as follows:
You are getting the alarm because the profile would be getting executed say every 2 mins (1 min more than scheduled interval i.e Heartbeat), which is within the profile timeout limit, but more than "delay_threshold" limit.
***The query timed out! alarm comes when the SQL Timeout in the profile is less than how long the query takes so please increase this value to some appropriate value.***
If you have a lot of QOS data/rows in the database tables, then a checkpoint may take more time which can lead to high profile execution time and hence result in timeout alarms.
You can configure the remaining timeouts based on the above explanation and the alarm you are getting.