Share via

Connection broker high availability

Anonymous
2023-07-01T12:37:58+00:00

I am trying to set up a connection broker of high availability. I know we can set it up using SQL database.

  1. Do we have any alternative ways to set up connection broker high availability without the SQL database, by having a batch process that can copy the database of Connection broker 1 to connection broker 2. And whereever connection broker 2 is required , we can use it as a active passive set up using windows failover cluster.

What are the disadvantages of this set up.

  1. Is there any other database we can use instead of SQL database.
Windows for home | Other | Apps

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-07-02T05:35:01+00:00

    Dear Server Question

    Hope you are doing great, I am aware of the present situation is that you need to implement high availability setup for Connection Broker without using SQL database.

    With great effort of inquiry, SQL server are beyond the supported scope of community, I can say with doubtless that your knowledge will be broader than mine in this regard.

    However, according to the Microsoft documentation, you can deploy a Remote Desktop Connection Broker (RD Connection Broker) cluster to improve the availability and scale of your Remote Desktop Services infrastructure. You can use Azure SQL Database instance or SQL Server in your local environment as the database for the Connection Broker. But you need to find the connection string for the database and make sure you have the correct ODBC driver. See the documentation below:

    Add an RD Connection Broker server to configure high availability in RDS | Microsoft Learn

    Alternatively, you can set up RDS without Connection Broker for a single-server installation, or configure a high availability Connection Broker deployment that uses dedicated SQL Server. However, these methods may have some drawbacks, such as limited scalability, performance issues, or increased complexity. See the documentation below:

    Remote Desktop service (RDS) Connection Broker or Remote Desktop Management service (RDMS) fails - Windows Server | Microsoft Learn

    Additionally, I could not find any information about using a batch process to copy the database of Connection Broker 1 to Connection Broker 2, or using any other database instead of SQL database. It seems that these options are not supported or recommended by Microsoft.

    For the most appropriate community for posting your issue shall be SQL Server - Microsoft Q&A, which it is a professional place consist of many technical experts or advanced users like you. Moreover, I will keep this thread opened in case our MVP/Volunteer moderator/ can have some targeted insights for you.

    Best regards,

    Chandy | Microsoft Community Support Specialist

    * Your patience and cooperation are highly appreciated.

    Was this answer helpful?

    0 comments