| Measurement |
Description |
Measurement Unit |
Interpretation |
| Login_rate |
Indicates the total number of logins per second. |
Login/Sec |
A high value here indicates an increase in the rate of user logins into the SQL server.
An unusual increase in the login rate may be an indicator of abnormal activity of database applications. |
| Logout_rate |
Indicates the total number of logouts per second. |
Logout/Sec |
A high value here indicates increase in rate of users logging out of SQL server.
An unusually large number of logins and logouts can occur due to application retries being caused by errors during database access. |
| Num_user_connections |
Indicates the number user connections to the server at an instant. |
Number |
As each user connection consumes some memory, a large number of user connections
could affect throughput. By tracking the history of user connections, a database administrator can set the maximum expected number of
concurrent users accordingly. |
| Logical_connections |
Indicates the number of logical connections to the server. |
Number |
The main purpose of logical connections is to service multiple active result sets (MARS) requests. For MARS requests, every time that an application makes a connection to SQL Server, there may be more than one logical connection that corresponds to a physical connection.
When MARS is not used, the ratio between physical and logical connections is 1:1. Therefore, every time that an application makes a connection to SQL Server, logical connections will increase by 1.
|