Connect a Google BigQuery database to your Stitch account as a destination.
Migrate from using Stitch’s Google BigQuery v1 destination to the new version, v2.
Using Google BigQuery
Unlike traditional relational databases and other cloud solutions, Google BigQuery pricing isn’t fixed-rate: it’s based on usage. The goal of this article is to help you better understand how your data warehousing costs will be impacted by using Stitch’s BigQuery destination so you can make an informed decision.
Want to improve your BigQuery performance and query costs? In this article, we’ll walk you through how to use table partitioning and clustering to streamline query processing in your BigQuery destination.
Understand how Stitch loads nested data structures in version 2 of the Google BigQuery destination.
In this article, we’ll cover how append-only replication works and how to account for it in your queries.
Destination Loading Error Reference Resolve errors related to loading data into your Stitch destination.
Destination Connection Error Reference Resolve errors related to connecting to your Stitch destination.
Reference documentation for version 2 of Stitch’s Google BigQuery destination, including info about Stitch features, replication, and transformations.
Learn how Stitch will load data from your integrations into version 2 of Stitch’s Google BigQuery destination.
Verify your integrations’ compatibility with your data warehouse.
When data is loaded into your destination, Stitch will create some additional columns and tables. Learn about these system columns and tables and how Stitch uses them.
A reference of Stitch and destination-reserved keywords.
Some of Stitch’s destinations don’t have native support for Primary Keys. To ensure data can be de-duped during loading, Stitch will create a Primary Keys table for each integration schema.