![]() |
VOOZH | about |
Looker Studio, formerly known as Google Data Studio, empowers users to craft customized reports featuring data visualizations that can be shared with clients while reflecting your brand identity. When combined with CData Connect AI, you gain immediate cloud-to-cloud access to AlloyDB data to create visualizations, dashboards, and more. This article provides step-by-step instructions on establishing a virtual database for AlloyDB and generating reports from AlloyDB data within Looker Studio.
CData Connect AI offers a seamless cloud-to-cloud interface tailored for AlloyDB, making it straightforward to construct reports directly from live AlloyDB data within Looker Studio without the need for data replication. As you create visualizations, Looker Studio generates queries to retrieve data. With its inherent optimized data processing capabilities, CData Connect AI efficiently channels all supported query operations, including filters, JOINs, and more, directly to AlloyDB. This leverages server-side processing to swiftly provide the requested AlloyDB data.
This article requires a CData Connect AI instance and the CData Connect AI Connector for Looker Studio. Get more information on the CData Connect AI and sign up for a free trial at https://www.cdata.com/cloud.
Connectivity to AlloyDB from Looker Studio is made possible through CData Connect AI. To work with AlloyDB data from Looker Studio, 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)
With the connection configured, you are ready to connect to AlloyDB data from Looker Studio.
The steps below outline connecting to CData Connect AI from Looker Studio to create a new AlloyDB data source and build a simple visualization from the data.
Now you have a direct, cloud-to-cloud connection to live AlloyDB data from your Looker Studio workbook. You can create more data sources and new visualizations, build reports, and more β all without replicating AlloyDB data.
Try CData Connect AI and get real-time data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial