VOOZH about

URL: https://www.cdata.com/kb/tech/alloydb-cloud-redash.rst

⇱ Query, Visualize, and Share live AlloyDB Data in Redash


Query, Visualize, and Share live AlloyDB Data in Redash

πŸ‘ Mohsin Turki
Mohsin Turki
Technical Marketing Engineer
Use CData Connect AI to connect to live AlloyDB data in Redash for querying, visualizing, and sharing.

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.

Configure AlloyDB Connectivity for Redash

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.

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. πŸ‘ Adding a Connection
  3. Select "AlloyDB" from the Add Connection panel
  4. πŸ‘ Selecting a data source
  5. Enter the necessary authentication properties to connect to AlloyDB.

    The following connection properties are usually required in order to connect to AlloyDB.

    • Server: The host name or IP of the server hosting the AlloyDB database.
    • User: The user which will be used to authenticate with the AlloyDB server.
    • Password: The password which will be used to authenticate with the AlloyDB server.

    You can also optionally set the following:

    • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
    • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

    Authenticating with Standard Authentication

    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.

    Authenticating with pg_hba.conf Auth Schemes

    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.

    Authenticating with MD5 Authentication

    This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

    Authenticating with SASL Authentication

    This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

    Authenticating with Kerberos

    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)

  6. Click Save & Test
  7. Navigate to the Permissions tab in the Add AlloyDB Connection page and update the User-based permissions. πŸ‘ Updating permissions

Add a Personal Access Token

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.

  1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
  2. On the Settings page, go to the Access Tokens section and click Create PAT.
  3. Give the PAT a name and click Create. πŸ‘ Creating a new PAT
  4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to AlloyDB data from Redash.

Connect to AlloyDB from Redash using Connect AI

To establish a connection from Redash to CData Connect AI using the Virtual SQL Server, follow these steps:

  1. Log into Redash.
  2. Click the settings widget on the top right.
  3. Click New Data Source.
  4. Select Microsoft SQL Server as the Data Source Type.
  5. On the configuration tab, set the following properties:
    • Database Name: enter the Connection Name of the CData Connect AI data source you want to connect to (for example, Salesforce1).
    • Server: enter the virtual SQL Server host name (tds.cdata.com)
    • User: enter your CData Connect AI username. This is displayed in the top-right corner of the CData Connect AI interface. For example, [email protected].
    • Password: enter the PAT you generated on the Settings page.
    • Port: enter 14333
    πŸ‘ Configuring the connection to Connect AI from Redash.
  6. Click Create.
  7. Click Test Connection to ensure that the connection is configured properly.

You can now work with live AlloyDB data in Redash.

Get CData Connect AI

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Redash, try CData Connect AI today!