Connect to Live Google Drive Data in PostGresSQL Interface through CData Connect AI

There are a vast number of PostgreSQL clients available on the Internet. PostgreSQL is a popular interface for data access. When you pair PostgreSQL with CData Connect AI, you gain database-like access to live Google Drive data from PostgreSQL. In this article, we walk through the process of connecting to Google Drive data in Connect AI and establishing a connection between Connect AI and PostgreSQL using a TDS foreign data wrapper (FDW).

CData Connect AI provides a pure SQL Server interface for Google Drive, allowing you to query data from Google Drive 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 Google Drive, leveraging server-side processing to return the requested Google Drive data quickly.

Connect to Google Drive in Connect AI

CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.

1. Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a Connection

2. Select "Google Drive" from the Add Connection panel
👁 Selecting a data source

3. Enter the necessary authentication properties to connect to Google Drive.

   You can connect to Google APIs on behalf of individual users or on behalf of a domain. Google uses the OAuth authentication standard. See the "Getting Started" section of the help documentation for a guide.

   👁 Configuring a connection (Salesforce is shown)
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add Google Drive 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 Google Drive data from PostgreSQL.

Build the TDS Foreign Data Wrapper

The Foreign Data Wrapper can be installed as an extension to PostgreSQL, without recompiling PostgreSQL. The tds_fdw extension is used as an example (https://github.com/tds-fdw/tds_fdw).

1. You can clone and build the git repository via something like the following view source:

   sudo apt-get install git
   git clone https://github.com/tds-fdw/tds_fdw.git
   cd tds_fdw
   make USE_PGXS=1
   sudo make USE_PGXS=1 install
   

   Note: If you have several PostgreSQL versions and you do not want to build for the default one, first locate where the binary for pg_config is, take note of the full path, and then append PG_CONFIG=
2. After you finish the installation, then start the server:

   sudo service postgresql start
   

3. Then go inside the Postgres database

   psql -h localhost -U postgres -d postgres
   

   Note: Instead of localhost you can put the IP where your PostgreSQL is hosted.

Connect to Google Drive data as a PostgreSQL Database and query the data!

After you have installed the extension, follow the steps below to start executing queries to Google Drive data:

1. Log into your database.
2. Load the extension for the database:

   CREATE EXTENSION tds_fdw;
   

3. Create a server object for Google Drive data:

   CREATE SERVER "GoogleDrive1" FOREIGN DATA WRAPPER tds_fdw OPTIONS (servername'tds.cdata.com', port '14333', database 'GoogleDrive1');
   

4. Configure user mapping with your email and Personal Access Token from your Connect AI account:

   CREATE USER MAPPING for postgres SERVER "GoogleDrive1" OPTIONS (username '[email protected]', password 'your_personal_access_token' );
   

5. Create the local schema:

   CREATE SCHEMA "GoogleDrive1";
   

6. Create a foreign table in your local database:

   #Using a table_name definition:
   
   CREATE FOREIGN TABLE "GoogleDrive1".Files ( 
   id varchar, 
   Size varchar) 
   SERVER "GoogleDrive1"
   OPTIONS(table_name 'GoogleDrive.Files', row_estimate_method 'showplan_all');
   
   #Or using a schema_name and table_name definition:
   
   CREATE FOREIGN TABLE "GoogleDrive1".Files ( 
   id varchar, 
   Size varchar) 
   SERVER "GoogleDrive1"
   OPTIONS (schema_name 'GoogleDrive', table_name 'Files', row_estimate_method 'showplan_all');
   
   #Or using a query definition:
   
   CREATE FOREIGN TABLE "GoogleDrive1".Files (
   id varchar, 
   Size varchar) 
   SERVER "GoogleDrive1"
   OPTIONS (query 'SELECT * FROM GoogleDrive.Files', row_estimate_method 'showplan_all');
   
   #Or setting a remote column name:
   
   CREATE FOREIGN TABLE "GoogleDrive1".Files (
   id varchar,
   col2 varchar OPTIONS (column_name 'Size'))
   SERVER "GoogleDrive1"
   OPTIONS (schema_name 'GoogleDrive', table_name 'Files', row_estimate_method 'showplan_all');
   

7. You can now execute read/write commands to Google Drive:

   SELECT id, Size
   FROM "GoogleDrive1".Files;
   

More Information & Free Trial

Now, you have created a simple query from live Google Drive data. For more information on connecting to Google Drive (and more than 200 other data sources), visit the Connect AI page. Sign up for a free trial and start working with live Google Drive data in PostgreSQL.