A Closer Look at the RD Connection Broker Database in Windows Server 2012
We're assuming that Windows Server 2012 RD Connection Broker High Availability (HA) has already been setup. The configuration process of setting up HA is covered in this wiki: Installing and Configuring RD Connection Broker High Availability in Windows Server 2012
In this wiki we'll take a closer look at the RD Connection Broker database itself to explore what is stored inside the database.
Before we continue note that modifying any data directly in the database is not supported by Microsoft and that it is not advised you to do so. This wiki is just intended to show you how information is stored in SQL by only doing Select (read) statements.
For example the table rds.ConnectionBroker contains all the RD Connection Broker of this environment and the last time alive signal was received.
http://virtualizationadmin.com/img/upl/image0111360786925267.png
Figure 1: SQL table rds.ConnectionBroker
There are several tables that hold information about which servers run which RDS roles. The table rds.server contains all the servers involved in the RDS environment, including their server ID.
http://virtualizationadmin.com/img/upl/image0121360786925267.png
Figure 2: SQL table rds.Server
This server ID is then used in a table per RDS Role, below as an example the rds.RoleRdsh table.
http://virtualizationadmin.com/img/upl/image0131360786925267.png
Figure 3: SQL table rds.RoleRdsh
The table rds.PoolProperty contains the settings on a Session Collection level. Session Collections are identified by the PoolId.
http://virtualizationadmin.com/img/upl/image0141360786944689.png
Figure 4: SQL table rds.PoolProperty
The table rds.DeploymentSetting contains the settings configured on a deployment level.
http://virtualizationadmin.com/img/upl/image0151360786925283.png
Figure 5: SQL table rds.DeploymentSetting
