Introduction to datasets

This page provides an overview of datasets in BigQuery.

Datasets

A dataset is contained within a specific project. Datasets are top-level containers that are used to organize and control access to your tables and views. A table or view must belong to a dataset, so you need to create at least one dataset before loading data into BigQuery.

Dataset limitations

BigQuery datasets are subject to the following limitations:

You can set the geographic location at creation time only. After a dataset has been created, the location becomes immutable and can't be changed in the GCP Console, the classic BigQuery web UI, the command-line tool, or by calling the patch or update API methods.
All tables referenced in a query must be stored in datasets in the same location.
When copying a table, the datasets containing the source table and destination table must reside in the same location.
Dataset names must be unique per project.
As you approach thousands of datasets in a project, classic UI performance begins to degrade, and listing datasets becomes slower.

Dataset quotas

For more information on dataset quotas and limits, see Quotas and limits.

Dataset pricing

You are not charged for creating, updating, or deleting a dataset.

For more information on BigQuery pricing, see Pricing.

Next steps

For more information on creating datasets, see Creating datasets.
For more information on assigning access controls to datasets, see Controlling access to datasets.

Was this page helpful? Let us know how we did:

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see our Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated February 4, 2019.