none
RDS 2016 HA and SQL Server 2017 AlwaysOn Availability Groups RRS feed

  • Question

  • Hello everyone.

    I have searched for official information without luck. I appreciate any input.

    We have a RDS 2016 farm with high availability (HA) connection brokers that connect to SQL Server 2014 AlwaysOn Failover Cluster. The connection Brokers have local installed "SQL Server Native Client".  I have not problems.

    We will migrate to SQL Server 2017 AlwaysOn Availability Groups. Questions:

    • SQL Server Native Client (used until SQL Server 2012) is deprecated, https://docs.microsoft.com/es-es/sql/relational-databases/native-client/sql-server-native-client?view=sql-server-2017. Could we use on the Connection Broker "Microsoft ODBC or OLE DB Driver for SQL Server"?
    • Could connection brokers use "SQL Server Native Client" and connect with SQL Server 2017 AlwaysOn Availability Groups?

    Any experience?

    Thanks.

    Friday, October 11, 2019 8:41 AM

Answers

  • HI
    Thank you for waiting again.
    1 Could we use on the Connection Broker "Microsoft ODBC or OLE DB Driver for SQL Server"?
    2 Could connection brokers use "SQL Server Native Client" and connect with SQL Server 2017 AlwaysOn Availability Groups?
    yes,sqlncli.msi have been removed from sql server feature pack 2017.
    on RDCB HA side,if you are using SQL 2017 in local network(on-premise),we guess we can still use native client for basic connection sql server.
    on RDCB HA side,if you are using SQL 2017 in cloud(like azure SQL) ,i think Microsoft ODBC Driver 17 for SQL Server is must.
    So no matter on-premise or cloud SQL ,we can use Microsoft ODBC Driver 17 as native client ,we can try to change it like below picture :

    Connection String: DRIVER=ODBC Driver 17 for SQL Server;SERVER=<name of SQL server>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=<name of database>

    There are documents for your reference
    Installing SQL Server Native Client
    https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/installing-sql-server-native-client?view=sql-server-ver15
    Microsoft® ODBC Driver 17 for SQL Server® - Windows, Linux, & macOS
    https://www.microsoft.com/en-us/download/details.aspx?id=56567
    Add the RD Connection Broker server to the deployment and configure high availability
    https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-connection-broker-cluster
    Microsoft OLE DB Driver for SQL Server
    https://docs.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-server-ver15
    Installing OLE DB Driver for SQL Server
    https://docs.microsoft.com/en-us/sql/connect/oledb/applications/installing-oledb-driver-for-sql-server?view=sql-server-ver15

    Connecting to SQL Server from Windows
    https://github.com/mkleehammer/pyodbc/wiki/Connecting-to-SQL-Server-from-Windows



    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.





    Wednesday, October 23, 2019 7:01 AM
    Moderator

All replies

  • HI
    I am researching your issue ,thanks for your waiting.

    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 15, 2019 9:40 AM
    Moderator
  • Thanks for you time.
    Monday, October 21, 2019 12:20 PM
  • HI
    Thank you for waiting again.
    1 Could we use on the Connection Broker "Microsoft ODBC or OLE DB Driver for SQL Server"?
    2 Could connection brokers use "SQL Server Native Client" and connect with SQL Server 2017 AlwaysOn Availability Groups?
    yes,sqlncli.msi have been removed from sql server feature pack 2017.
    on RDCB HA side,if you are using SQL 2017 in local network(on-premise),we guess we can still use native client for basic connection sql server.
    on RDCB HA side,if you are using SQL 2017 in cloud(like azure SQL) ,i think Microsoft ODBC Driver 17 for SQL Server is must.
    So no matter on-premise or cloud SQL ,we can use Microsoft ODBC Driver 17 as native client ,we can try to change it like below picture :

    Connection String: DRIVER=ODBC Driver 17 for SQL Server;SERVER=<name of SQL server>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=<name of database>

    There are documents for your reference
    Installing SQL Server Native Client
    https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/installing-sql-server-native-client?view=sql-server-ver15
    Microsoft® ODBC Driver 17 for SQL Server® - Windows, Linux, & macOS
    https://www.microsoft.com/en-us/download/details.aspx?id=56567
    Add the RD Connection Broker server to the deployment and configure high availability
    https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-connection-broker-cluster
    Microsoft OLE DB Driver for SQL Server
    https://docs.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-server-ver15
    Installing OLE DB Driver for SQL Server
    https://docs.microsoft.com/en-us/sql/connect/oledb/applications/installing-oledb-driver-for-sql-server?view=sql-server-ver15

    Connecting to SQL Server from Windows
    https://github.com/mkleehammer/pyodbc/wiki/Connecting-to-SQL-Server-from-Windows



    Best Regards
    Andy YOU
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.





    Wednesday, October 23, 2019 7:01 AM
    Moderator
  • Perfect!. Thanks for your time.
    Friday, October 25, 2019 5:23 AM