| Measurement |
Description |
Measurement Unit |
Interpretation |
| DeadLocks |
The current number of deadlocks on the Microsoft SQL server |
Number |
The SQL error log will capture deadlock conditions only if trace is enabled on the SQL server. This means that if the value of this measure is 0, it could imply one of the following:
Tracing is not enabled, and therefore, the SQL error log is not able to capture any deadlock conditions; if you want, you can enable tracing by runing the following command from the SQL prompt:
DBCC TRACEON(1222,-1) Tracing is enabled, but no deadlock has occurred. This is a sign of good health.
If this measure reports a non-zero value on the other hand, it is a cause for concern, as it indicates that one/more deadlocks have occurred. In this case, you can use the detailed diagnosis of this test to know more information about the deadlocks.
|
| Informational_messages |
The number of informational messages that were currently captured by the error log |
Number |
Messages with a severity level of 0 to 10 are informational messages and not actual errors. |
| User_errors |
The number of user errors that were captured currently by the error log |
Number |
The value of this measure indicates the number of errors with a severity level between 11 and 16. Such errors are generated as a result of user problems and can be fixed by the user. |
| Software_errors |
The number of software errors captured by the error log currently |
Number |
All errors with severity levels 17 to 19 will be counted as software errors.
Severity level 17 indicates that SQL Server has run out of a configurable resource, such as locks. Severity error 17 can be corrected by the DBA, and in some cases, by the database owner. Severity level 18 messages indicate non-fatal internal software problems. Severity level 19 indicates that a nonconfigurable resource limit has been exceeded. |
| Hardware_errors |
The number of hardware errors currently experienced by the target Microsoft SQL server |
Number |
Errors with severity levels 20 to 25 are typically categorized as hardware errors.
Severity level 20 indicates a problem with a statement issued by the current process.Severity level 21 indicates that SQL Server has encountered a problem that affects all the processes in a database.Severity level 22 means a table or index has been damaged. To try to determine the extent of the problem, stop and restart SQL Server. If the problem is in the cache and not on the disk, the restart corrects the problem. Otherwise, use DBCC to determine the extent of the damage and the required action to take.Severity level 23 indicates a suspect database. To determine the extent of the damage and the proper action to take, use the DBCC commands.Severity level 24 indicates a hardware problem.Severity level 25 indicates some type of system error. |
| Other_errors |
The number of other errors in the Microsoft SQL server. |
Number |
|
| Num_of_warnings |
Indicates the number of warning messages found in the SQL error logs during the last measurement period. |
Number |
|
| File_Size |
Indicates the current size of the SQL error log file. |
MB |
|
| Growth_rate |
Indicates the rate at which the SQL error log file is growing. |
MB/Sec |
A high value for this measure or a consistent increase in its value indicates that the SQL error log is rapidly growing and may end up occupying too much space on the volume.
Under such circumstances, it is recommended that you delete the SQL error file and then issue a log file switch, so that MS SQL automatically creates a new SQL error log file for you the next time a database activity needs to be logged. |
| Login_success |
Indicates the number of successful logins to the server during the last measurement period. |
Number |
This measure is a good indicator of the overall health of the server. The detailed diagnosis of this measure lists the login time, SPID and the message.
If this measure does not report valid metrics, ensure that the Both failed and successful logins flag under the Login auditing section that appears when the Security option in the Security Properties page of the target Microsoft SQL server is enabled. |