![]() |
VOOZH | about |
Redash is a collaboration tool that lets you query, visualize, and share your data. When paired with CData Connect AI, Redash gets access to live AlloyDB data. This article demonstrates how to connect to AlloyDB using Connect AI and work with live AlloyDB data in Redash.
CData Connect AI provides a pure SQL Server interface for AlloyDB, allowing you to query data from AlloyDB without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to AlloyDB, leveraging server-side processing to return the requested AlloyDB data quickly.
Connectivity to AlloyDB from Redash is made possible through CData Connect AI. To work with AlloyDB data in Redash, we start by creating and configuring a AlloyDB connection.
The following connection properties are usually required in order to connect to AlloyDB.
You can also optionally set the following:
Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.
No further action is required to leverage Standard Authentication to connect.
There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.
Find instructions about authentication setup on the AlloyDB Server here.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.
The authentication with Kerberos is initiated by AlloyDB Server when the β is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.
π Configuring a connection (Salesforce is shown)
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
With the connection configured and a PAT generated, you are ready to connect to AlloyDB data from Redash.
To establish a connection from Redash to CData Connect AI using the Virtual SQL Server, follow these steps:
You can now work with live AlloyDB data in Redash.
To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Redash, try CData Connect AI today!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial