gcloud alpha bq datasets create Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud alpha bq datasets create - create a new BigQuery dataset
- SYNOPSIS
gcloud alpha bq datasets createDATASET[--description=DESCRIPTION][--overwrite][--permissions-file=[PERMISSIONS_FILE,…]][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
(ALPHA)Create a new BigQuery dataset.- EXAMPLES
- The following command creates a dataset with ID
my-datasetgcloudalphabqdatasetscreatemy-dataset--description'My New Dataset'The following command creates a dataset with ID
my-other-dataset,overwritting destination if it exists:gcloudalphabqdatasetscreatemy-other-dataset--description'My Other Dataset'--overwrite - POSITIONAL ARGUMENTS
- Dataset resource - ID of the the dataset being created. The ID must contain onlyletters (a-z, A-Z), numbers (0-9), or underscores ( _ ). The maximum length is1,024 characters. This represents a Cloud resource. (NOTE) Some attributes arenot given arguments in this group but can be set in other ways.
To set the
projectattribute:- provide the argument
dataseton the command line with a fullyspecified name; - provide the argument
--projecton the command line; - set the property
core/project.
This must be specified.
DATASET- ID of the dataset or fully qualified identifier for the dataset.
To set the
datasetattribute:- provide the argument
dataseton the command line.
- provide the argument
- provide the argument
- Dataset resource - ID of the the dataset being created. The ID must contain onlyletters (a-z, A-Z), numbers (0-9), or underscores ( _ ). The maximum length is1,024 characters. This represents a Cloud resource. (NOTE) Some attributes arenot given arguments in this group but can be set in other ways.
- FLAGS
--description=DESCRIPTION- Description of the dataset.
--overwrite- Overwrite if the resource already exists.
--permissions-file=[PERMISSIONS_FILE,…]- A local yaml or JSON file containing the access permissions specifying who isallowed to access the data.
YamlfFile should be specified the form:\ access:
- role: ROLE [access type]: ACCESS_VALUE
- …
and JSON file should be specified in the form: {"access": [ { "role": "ROLE","[access type]": "ACCESS_VALUE" }, … ]}
Where
access typeis one of:domain,userByEmail,specialGrouporview.If this field is not specified, BigQuery adds these default dataset accesspermissions at creation time in :
- specialGroup=projectReaders, role=READER
- specialGroup=projectWriters, role=WRITER
- specialGroup=projectOwners, role=OWNER
- userByEmail=[dataset creator email], role=OWNER
For more information on BigQuery permissions see:https://cloud.google.com/bigquery/docs/access-control
- GCLOUD WIDE FLAGS
- These flags are available to all commands:
--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.Run
$gcloud helpfor details. - API REFERENCE
- This command uses the
bigquery/v2API. The full documentation forthis API can be found at:https://cloud.google.com/bigquery/ - NOTES
- This command is currently in alpha and might change without notice. If thiscommand fails with API permission errors despite specifying the correct project,you might be trying to access an API with an invitation-only early accessallowlist.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-05-07 UTC.