Client Connectivity

This chapter describes how client tools and applications connect to Querona: you point a BI tool, driver or application at Querona as if it were a SQL Server instance, and Querona serves the data. Here Querona is the server.

For the opposite direction — Querona connecting out to your data sources — see Connections.

Note

Querona emulates Microsoft SQL Server. Consequently, client connectivity is handled using drivers built into the client.

To be able to connect you have to know the Querona server name and port that was configured for data access.

Information about the server and port is available from the dashboard, section “Interfaces” or it can be read from dashboard section “How to connect data tool to Querona.” Port 1433 is a default port for connectivity, and it can be omitted in a client connection dialog of your tool. For more information, please refer to the section below and your tool documentation.

Here is the list of popular client software along with instructions on how to connect them to Querona:

• Connecting from Excel
• Connecting from PowerBI
• Connecting from Tableau
• Connecting from SQL Server using Linked Server
• Connecting from Python
• Connecting from Rtools and RStudio

Configure the client to use Strict connection encryption

If Querona is configured to require Strict connection encryption, all clients have to support it, or connection will be refused.

Remarks

If you see SSL certificate validation failed, ensure that:

• Server certificate is valid on the machine you’re using for testing

• At least one of the following is true:

  • Provider SQL Server matches CA name or one of the DNS names in the certificate.

  • HostNameInCertificate connection string property matches CA name or one of the DNS names in the certificate.

JDBC

To configure the Microsoft JDBC driver see Microsoft’s article Connecting with encryption.