RD Connection Broker Database Test
The RD Connection Broker database stores information about the user sessions, session states, and session routing. This database is typically used to store session information, manage session load balancing, and support re-connections.
This test monitors the RD connection broker database and reports the number of stored procedure calls that had failed. In addition, this test reports the number of sessions that are active/waiting. An abnormally high number of active/waiting sessions will lead to performance issues.
Target of the test : Microsoft RD Connection Broker
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each RD connection broker database in a Microsoft RD Connection Broker that is currently launched.
Parameters | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The nick name of the Microsoft RD Connection Broker component for which this test is to be configured. |
Port |
Refers to the port at which the specified host listens to. By default, this is 3389. |
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Active contexts |
Indicates the number of active contexts in this database. |
Number |
An active context typically refers to an active session in the system, where a user is currently logged in or interacting with a remote desktop environment. If the number of active sessions exceeds the capacity of the RD environment, it can lead to issues related to performance, resource exhaustion, and user experience. |
Waiting contexts |
Indicates the number of waiting contexts in this database. |
Number |
A waiting context represents a session request that is currently in a "queued" or "waiting" state, unable to be assigned to an RD Session Host or VM due to resource constraints, load balancing, or other issues. A high number of waiting contexts can indicate problems with capacity, performance, or load distribution, which may require scaling the environment or troubleshooting configuration issues. |
Avg stored procedure call execution time |
Indicates the average amount of time taken to execute a stored procedure call in this database. |
Seconds |
The value of this measure refers to the amount of time it takes for the stored procedure to run from the moment it is called until it finishes executing. |
Avg stored procedure call wait time |
Indicates the average time a stored procedure call waits in this database. |
Seconds |
A low value of this measure is desired. |
Total stored procedure calls |
Indicates the total number of stored procedure calls in this database. |
Number |
|
Failed stored procedure calls |
Indicates the total number of stored procedure calls in this database that had failed during the last measurement period. |
Number |
A low value of this measure is desired.
|
Recent failed stored procedure calls |
Indicates the percentage of stored procedure calls in this database that had failed recently during the last measurement period. |
Percent |