Pricing

Unlike many other cloud-based data warehouse solutions, BigQuery’s pricing model is based on usage and not a fixed-rate. This means that your bill can vary over time.

Before fully committing yourself to using BigQuery as your data warehouse, we recommend familiarizing yourself with the BigQuery pricing model and how using Stitch may impact your costs.

Learn more about Stitch & BigQuery pricing


Setup info

High-level details about Stitch’s implementation of BigQuery, such as supported connection methods, availability on Stitch plans, etc.

Release status

Released

Pricing tier

All Stitch plans

Supported versions

Not applicable

Supported regions

Stitch supports the following Google Storage Location regions:

  • United States (US)

  • European Union (EU)

  • London (europe-west2)

  • Singapore (asia-southeast)

  • Tokyo (asia-northeast)

  • Sydney (australia-southeast)

SSH connections

Unsupported

Stitch does not support using SSH tunnels to connect to BigQuery destinations.

SSL connections

Supported

Stitch will attempt to use SSL to connect by default. No additional configuration is needed on your part.

VPN connections

Unsupported

Workload and performance management

Supported

To improve your query performance, you can apply partitioning and/or clustering to Stitch-created tables in your BigQuery destination. Your settings will remain intact even when new data is loaded.

Refer to the Table partitioning and clustering guide for application instructions.

Setup documentation


Replication

Details about Stitch and replication for BigQuery destinations.

Incremental Replication - Upserts

Unsupported

BigQuery destinations do not currently support upserts, or updating existing rows.

When Stitch loads data into BigQuery destinations, it will load it in an append-only fashion. This means that new records and updates to existing records are appended to the end of tables as new rows. Existing records are never updated.

More info and examples can be found in our Replication Method documentation and Append-Only querying guide.

Primary Keys

Unsupported

BigQuery destinations do not have native support for Primary Keys.

Multipe data types

Unsupported

BigQuery destinations do not support multiple data types in a single column.

To accommodate this scenario, Stitch will create additional columns for each data type. Refer to the Table structural changes guide for examples and more info.

Nested data structure support

Supported

BigQuery destinations natively support nested data structures.

More info and examples can be found in BigQuery’s documentation.

Incompatible sources

No reported incompatibilities

No integration compatibility issues have been reported for BigQuery.


Limitations

In this section:

  • Object name limits - Details about object naming rules imposed by BigQuery destinations.

  • Table limits - Details about table rules imposed by BigQuery destinations.

  • Data limits - Details about data limitations imposed by BigQuery destinations.

  • Column naming - Details about transformations performed by Stitch to ensure source column names adhere to the object naming rules imposed by BigQuery destinations.

Object name limits

Details about object naming rules imposed by BigQuery destinations.

Case sensitivity

Insensitive

This means that BigQuery destinations treat upper- and lowercase characters as the same. For example: CUSTOMERID and customerid are equal in BigQuery.

When column names are loaded into Redshift, any uppercase characters will be forced into lowercase. This means that Id and id will canonicalize to the same name, which can lead to object collision errors. Refer to the Column naming section of this guide for examples.

Reserved keywords

Object names must observe the reserved keywords in BigQuery’s documentation and Stitch’s set of reserved keywords.

Tables and columns with names that contain reserved keywords may be logged in the _sdc_rejected table.

Table name length

1,024 characters

Tables with names that exceed this limit will be rejected. Rejected tables are logged in the _sdc_rejected table.

Column name length

128 characters

Columns with names that exceed this limit will be rejected. Rejected columns are logged in the _sdc_rejected table.

Table limits

Details about table rules imposed by BigQuery destinations.

Max # of columns per table

10,000 columns

Max # of tables per database

None

Data limits

Details about data limitations imposed by BigQuery destinations.

Max record size

4 MB

Records that exceed this limit will be rejected. Rejected columns are logged in the _sdc_rejected table.

Timezone support

Unsupported

BigQuery will store the value in UTC as TIMESTAMP.

More info about timestamp data types can be found in BigQuery’s documentation.

Date ranges

0001-01-01 to 9999-12-31

Date values outside of this range will be rejected and logged in the sdc_rejected table.

More info about BigQuery date data types can be found in BigQuery’s documentation.

Timestamp ranges

0001-01-01 00:00:00 to 9999-12-31 23:59:59.999999 UTC

Timestamp values outside of this range will be rejected and logged in the sdc_rejected table.

More info about BigQuery time data types can be found in BigQuery’s documentation.

Integer range

-9,223,372,036,854,775,808 to 9,223,372,036,854,775,807

Integer values outside of this range will be rejected and logged in the _sdc_rejected table.

Decimal precision

Up to 38 digits of precision

Decimal values outside of this range will be rejected and logged in the _sdc_rejected table.

Decimal scale

Up to 9 digits of scale

Decimal values outside of this range will be rejected and logged in the _sdc_rejected table.

VARCHAR max width

None

While there aren’t any size limits on string data, the record as a whole must still be less than 4 MB or it will be rejected and logged in the _sdc_rejected table.

Column naming

Details about transformations performed by Stitch to ensure source column names adhere to the object naming rules imposed by BigQuery destinations.

Source column name Destination column name
Mixed case CuStOmErID customerid
Contains spaces customer id customer_id
Contains unsupported characters !customer#id _customer_id
Name begins with an underscore _customerid _customerid
Name begins with a non-letter 123customerid customerid

Compare destinations

Not sure if BigQuery is the data warehouse for you? Check out the Choosing a Stitch Destination guide to compare each of Stitch’s destination offerings.


Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.