How to load data from PostgreSQL to Google BigQuery
Access your data on PostgreSQL
The first step in migrating your PostgreSQL data to any data warehouse solution is accessing and extracting it. There are many ways of doing this like, for example, logical replication log as previously mentioned.
You need to listen to the log for changes on the database and reflect them on the target system. When pulling data from a database, you also need to filter tables, columns, find a way to identify updates and replicate the appropriate database schema considering that it will end up in a columnar database for analytics.
Another way is by using a JDBC importer. In this case, any input configuration will contain all the appropriate values for the database authentication and connection. By appropriately configuring the JDBC importer, you can control each table's behavior during import and alter its schema as well, if desired. Moreover, pagination of data importing can be simulated by querying tables in batching mode.
Transform and prepare your PostgreSQL data
After you have accessed your data on PostgreSQL, you will have to transform it based on two main factors:
- The limitations of the database that you will load the data into
- The type of analysis that you plan to perform
Each system has specific limitations on the data types and data structures that it supports. Also, you have to choose the right data types. Again, depending on the system you will send the data to, you will have to make the right choices.
For the most common data types, the mapping choices may seem to be obvious. Each database system will mostly support a set of more sophisticated and database-specific types whose mapping choices require careful consideration. This factor is quite important because it can limit your queries' expressivity directly out of the database.
However, plan to push the data to another PostgreSQL database. You probably don't have to worry about the data types unless you have some reasons for the analysis you will perform.
No matter your company's product, the chances are your production PostgreSQL database will hold almost all of the valuable data.
This data needs to be further analyzed from the users' interaction with your platform or e-shop to product descriptions and user-generated events. This analysis is required to identify the aspects of the product you need to focus on and the most commonly faced problems related to extra traction and more users.
You will also want to enrich this data with other data from your ticketing system, your accounting software, or your marketing platform.
Having all the data stored in a database dedicated to performing analytics, you can:
- Generate on-going reports by calculating the key performance indicators that matter the most to you
- Develop and test predictive applications aiming to automate the company's core business tasks
- Connect with your preferred business intelligence tool and create interactive dashboards to communicate the insights you have derived across all teams.
Load data from PostgreSQL to Google BigQuery
If you want to load PostgreSQL data to Google BigQuery, you have to use one of the following supported data sources:
- Google Cloud Storage
- Sent data directly to BigQuery with a POST request
- Google Cloud Datastore Backup
- Streaming insert
- App Engine log files
- Cloud Storage logs
From the above list of sources, 5 and 6 are not applicable in our case.
For Google Cloud Storage, you first have to load your data into it; there are a few options on how to do this. For example, you can use the console directly as described here, and do not forget to follow the best practices.
Another option is to post your data through the JSON API. As we see again, APIs play an important role in both the extraction and the loading of data into our data warehouse. It's just a matter of one HTTP POST request using a tool like CURL or Postman in its simplest case.
After you have loaded your data into Google Cloud Storage, you have to create a Load Job for BigQuery to load the data into it. This job should point to the source data in Cloud Storage that has to be imported. You can do this by providing source URIs that point to the appropriate objects.
The best way to load data from PostgreSQL to Google BigQuery and possible alternatives
In this post, we just scraped the surface of what can be done with Google BigQuery and how to load data into it. The way to proceed relies heavily on the data you want to load, the service from which it is coming from, and your use case's requirements. However, things can get even more complicated if you want to integrate data coming from different sources.
Instead of writing, hosting, and maintaining a flexible data infrastructure, a possible alternative is to use a product like RudderStack that can handle this kind of problem automatically for you.
RudderStack integrates seamlessly with multiple sources or services like databases, CRM, email campaigns, analytics, and more. Now you can quickly and safely move all your data from PostgreSQL into Google BigQuery and start generating insights from your data in no time.
Easily sync your product data from PostgreSQL into your Analytics data warehouse without affecting your live product system and combine it with your Sales, Marketing, Support, and Finance data to transform your business insights.
Don't want to go through the pain of direct integration? RudderStack's Reverse ETL connection makes it easy to send data from PostgreSQL to Google BigQuery.