Manage tables
This document describes how to manage tables in BigQuery. You can manage your BigQuery tables in the following ways:
For more information about creating and using tables including getting table information, listing tables, and controlling access to table data, see Creating and using tables.
Before you begin
Grant Identity and Access Management (IAM) roles that give users the necessary permissions to perform each task in this document. The permissions required to perform a task (if any) are listed in the "Required permissions" section of the task.
Update table properties
You can update the following elements of a table:
Required permissions
To update a table, you need the following IAM permissions:
bigquery.tables.update
bigquery.tables.get
Each of the following predefined IAM roles includes the permissions that you need in order to update a table:
roles/bigquery.dataEditor
roles/bigquery.dataOwner
roles/bigquery.admin
Additionally, if you have the bigquery.datasets.create
permission, you can
update the properties of the tables of the datasets that you create.
For more information about IAM roles and permissions in BigQuery, see Predefined roles and permissions.
Update a table's description
You can update a table's description in the following ways:
- Using the Google Cloud console.
- Using a data definition language (DDL)
ALTER TABLE
statement. - Using the
bq
command-line tool'sbq update
command. - Calling the
tables.patch
API method. - Using the client libraries.
To update a table's description:
Console
You cannot add a description when you create a table using the Google Cloud console. After the table is created, you can add a description on the Details page.
In the Explorer panel, expand your project and dataset, then select the table.
In the details panel, click Details.
In the Description section, click the pencil icon to edit the description.
Enter a description in the box, and click Update to save.
SQL
Use the
ALTER TABLE SET OPTIONS
statement.
The following example updates the
description of a table named mytable
:
In the Google Cloud console, go to the BigQuery page.
In the query editor, enter the following statement:
ALTER TABLE mydataset.mytable SET OPTIONS ( description = 'Description of mytable');
Click
Run.
For more information about how to run queries, see Running interactive queries.
bq
Issue the bq update
command with the --description
flag. If you are
updating a table in a project other than your default project, add the
project ID to the dataset name in the following format:
project_id:dataset
.
bq update \ --description "description" \ project_id:dataset.table
Replace the following:
description
: the text describing the table in quotesproject_id
: your project IDdataset
: the name of the dataset that contains the table you're updatingtable
: the name of the table you're updating
Examples:
To change the description of the mytable
table in the mydataset
dataset to
"Description of mytable", enter the following command. The mydataset
dataset is in
your default project.
bq update --description "Description of mytable" mydataset.mytable
To change the description of the mytable
table in the mydataset
dataset to
"Description of mytable", enter the following command. The mydataset
dataset is in the
myotherproject
project, not your default project.
bq update \
--description "Description of mytable" \
myotherproject:mydataset.mytable
API
Call the tables.patch
method and use the description
property in the table resource
to update the table's description. Because the tables.update
method
replaces the entire table resource, the tables.patch
method is preferred.
Go
Before trying this sample, follow the Go setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Go API
reference documentation.
Java
Before trying this sample, follow the Java setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Java API
reference documentation.
Python
Before trying this sample, follow the Python setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Python API
reference documentation.
Update a table's expiration time
You can set a default table expiration time at the dataset level, or you can set a table's expiration time when the table is created. A table's expiration time is often referred to as "time to live" or TTL.
When a table expires, it is deleted along with all of the data it contains. If necessary, you can undelete the expired table within the time travel window specified for the dataset, see Restore deleted tables for more information.
If you set the expiration when the table is created, the dataset's default table expiration is ignored. If you do not set a default table expiration at the dataset level, and you do not set a table expiration when the table is created, the table never expires and you must delete the table manually.
At any point after the table is created, you can update the table's expiration time in the following ways:
- Using the Google Cloud console.
- Using a data definition language (DDL)
ALTER TABLE
statement. - Using the
bq
command-line tool'sbq update
command. - Calling the
tables.patch
API method. - Using the client libraries.
To update a table's expiration time:
Console
You cannot add an expiration time when you create a table using the Google Cloud console. After a table is created, you can add or update a table expiration on the Table Details page.
In the Explorer panel, expand your project and dataset, then select the table.
In the details panel, click Details.
Click the pencil icon next to Table info
For Table expiration, select Specify date. Then select the expiration date using the calendar widget.
Click Update to save. The updated expiration time appears in the Table info section.
SQL
Use the
ALTER TABLE SET OPTIONS
statement.
The following example updates the
expiration time of a table named mytable
:
In the Google Cloud console, go to the BigQuery page.
In the query editor, enter the following statement:
ALTER TABLE mydataset.mytable SET OPTIONS ( -- Sets table expiration to timestamp 2025-02-03 12:34:56 expiration_timestamp = TIMESTAMP '2025-02-03 12:34:56');
Click
Run.
For more information about how to run queries, see Running interactive queries.
bq
Issue the bq update
command with the --expiration
flag. If you are
updating a table in a project other than your default project,
add the project ID to the dataset name in the following format:
project_id:dataset
.
bq update \
--expiration integer \
project_id:dataset.table
Replace the following:
integer
: the default lifetime (in seconds) for the table. The minimum value is 3600 seconds (one hour). The expiration time evaluates to the current time plus the integer value. If you specify0
, the table expiration is removed, and the table never expires. Tables with no expiration must be manually deleted.project_id
: your project ID.dataset
: the name of the dataset that contains the table you're updating.table
: the name of the table you're updating.
Examples:
To update the expiration time of the mytable
table in the mydataset
dataset to 5 days
(432000 seconds), enter the following command. The mydataset
dataset is in your
default project.
bq update --expiration 432000 mydataset.mytable
To update the expiration time of the mytable
table in the mydataset
dataset to 5 days
(432000 seconds), enter the following command. The mydataset
dataset is in the
myotherproject
project, not your default project.
bq update --expiration 432000 myotherproject:mydataset.mytable
API
Call the tables.patch
method and use the expirationTime
property in the table resource
to update the table expiration in milliseconds. Because the tables.update
method replaces the entire table resource, the tables.patch
method is
preferred.
Go
Before trying this sample, follow the Go setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Go API
reference documentation.
Java
Before trying this sample, follow the Java setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Java API
reference documentation.
Node.js
Before trying this sample, follow the Node.js setup instructions in the BigQuery quickstart using client libraries. For more information, see the BigQuery Node.js API reference documentation.
Python
Before trying this sample, follow the Python setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Python API
reference documentation.
To update the default dataset partition expiration time:
Java
Before trying this sample, follow the Java setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Java API
reference documentation.
Python
Before trying this sample, follow the Python setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Python API
reference documentation.
Update a table's schema definition
For more information about updating a table's schema definition, see Modifying table schemas.
Rename a table
You can rename a table after it has been created by using the
ALTER TABLE RENAME TO
statement.
The following example renames mytable
to mynewtable
:
ALTER TABLE mydataset.mytable
RENAME TO mynewtable;
Limitations on renaming tables
- If you want to rename a table that has data streaming into it, you must stop the streaming and wait for BigQuery to indicate that streaming is not in use.
- A table can usually be renamed within 72 hours of the last streaming operation, but it might take longer.
- Table ACLs and row access policies are not always preserved after a table is renamed.
- You can't concurrently rename a table and run a DML statement on that table.
- Renaming a table removes all Data Catalog tags on the table.
- You can't rename external tables.
Copy a table
This section describes how to create a full copy of a table. For information about other types of table copies, see table clones and table snapshots.
You can copy a table in the following ways:
- Use the Google Cloud console.
- Use the
bq cp
command. - Use a data definition language (DDL)
CREATE TABLE COPY
statement. - Call the jobs.insert
API method and configure a
copy
job. - Use the client libraries.
Limitations on copying tables
Table copy jobs are subject to the following limitations:
- When you copy a table, the name of the destination table must adhere to the same naming conventions as when you create a table.
- Table copies are subject to BigQuery limits on copy jobs.
- The Google Cloud console supports copying only one table at a time. You cannot overwrite an existing table in the destination dataset. The table must have a unique name in the destination dataset.
- When copying tables, the destination dataset must reside in the same location as the dataset containing the table being copied. For example, you cannot copy a table from an EU-based dataset and write it to a US-based dataset.
- Copying multiple source tables into a destination table is not supported by the Google Cloud console.
- When copying multiple source tables to a destination table using the API,
bq
command-line tool, or the client libraries, all source tables must have identical schemas. - The time that BigQuery takes to copy tables might vary significantly across different runs because the underlying storage is managed dynamically.
- You cannot copy and append a source table to a destination table that has more
columns than the source table, and the additional columns have
default values. Instead, you can run
INSERT destination_table SELECT * FROM source_table
to copy over the data.
Required permissions
To perform the tasks in this document, you need the following permissions.
Permissions to copy tables and partitions
To copy tables and partitions, you need IAM permissions on the source and destination datasets.
On the source dataset, you need the following:
bigquery.tables.get
bigquery.tables.getData
On the destination dataset, you need the following:
bigquery.tables.create
: This permission lets you create a copy of the table or partition in the destination dataset.
Each of the following predefined IAM roles includes the permissions that you need in order to copy tables and partitions:
roles/bigquery.dataEditor
roles/bigquery.dataOwner
roles/bigquery.admin
Permission to run a copy job
To run a copy job, you need the bigquery.jobs.create
IAM permission.
Each of the following predefined IAM roles includes the permissions that you need to run a copy job:
roles/bigquery.user
roles/bigquery.jobUser
roles/bigquery.admin
Additionally, if you have the bigquery.datasets.create
permission, you can
copy tables and partitions in the datasets that you create. You also need the
access to the destination dataset.
For more information on IAM roles and permissions in BigQuery, see Predefined roles and permissions.
Copy a single source table
You can copy a single table in the following ways:
- Using the Google Cloud console.
- Using the
bq
command-line tool'sbq cp
command. - Using a data definition language (DDL)
CREATE TABLE COPY
statement. - Calling the
jobs.insert
API method, configuring acopy
job, and specifying thesourceTable
property. - Using the client libraries.
The Google Cloud console and the CREATE TABLE COPY
statement support only
one source table and one destination
table in a copy job. To copy multiple source files
to a destination table, you must use the bq
command-line tool or the API.
To copy a single source table:
Console
In the Explorer panel, expand your project and dataset, then select the table.
In the details panel, click Copy table.
In the Copy table dialog, under Destination:
- For Project name, choose the project that will store the copied table.
- For Dataset name, select the dataset where you want to store the copied table. The source and destination datasets must be in the same location.
- For Table name, enter a name for the new table. The name must be unique in the destination dataset. You cannot overwrite an existing table in the destination dataset using the Google Cloud console. For more information about table name requirements, see Table naming.
Click Copy to start the copy job.
SQL
Use the
CREATE TABLE COPY
statement
to copy a table named
table1
to a new table named table1copy
:
In the Google Cloud console, go to the BigQuery page.
In the query editor, enter the following statement:
CREATE TABLE
myproject.mydataset.table1copy
COPYmyproject.mydataset.table1
;Click
Run.
For more information about how to run queries, see Running interactive queries.
bq
Issue the bq cp
command. Optional flags can be used to control the write
disposition of the destination table:
-a
or--append_table
appends the data from the source table to an existing table in the destination dataset.-f
or--force
overwrites an existing table in the destination dataset and doesn't prompt you for confirmation.-n
or--no_clobber
returns the following error message if the table exists in the destination dataset:Table 'project_id:dataset.table' already exists, skipping.
If-n
is not specified, the default behavior is to prompt you to choose whether to replace the destination table.--destination_kms_key
is the customer-managed Cloud KMS key used to encrypt the destination table.
--destination_kms_key
is not demonstrated here. See
Protecting data with Cloud Key Management Service keys
for more information.
If the source or destination dataset is in a project other than your default
project, add the project ID to the dataset names in the following format:
project_id:dataset
.
(Optional) Supply the --location
flag and set the value to your
location.
bq --location=location cp \ -a -f -n \project_id:dataset.source_table
\project_id:dataset.destination_table
Replace the following:
location
: the name of your location. The--location
flag is optional. For example, if you are using BigQuery in the Tokyo region, you can set the flag's value toasia-northeast1
. You can set a default value for the location using the.bigqueryrc
file.project_id
: your project ID.dataset
: the name of the source or destination dataset.source_table
: the table you're copying.destination_table
: the name of the table in the destination dataset.
Examples:
To copy the mydataset.mytable
table to the mydataset2.mytable2
table,
enter the following command. Both datasets are in your default project.
bq cp mydataset.mytable mydataset2.mytable2
To copy the mydataset.mytable
table and to overwrite a destination table
with the same name, enter the following command. The source dataset is in
your default project. The destination dataset is in the myotherproject
project. The -f
shortcut is used to overwrite the destination table
without a prompt.
bq cp -f \
mydataset.mytable \
myotherproject:myotherdataset.mytable
To copy the mydataset.mytable
table and to return an error if the
destination dataset contains a table with the same name, enter the following
command. The source dataset is in your default project. The destination
dataset is in the myotherproject
project. The -n
shortcut is used to
prevent overwriting a table with the same name.
bq cp -n \
mydataset.mytable \
myotherproject:myotherdataset.mytable
To copy the mydataset.mytable
table and to append the data to a
destination table with the same name, enter the following command. The
source dataset is in your default project. The destination dataset is in the
myotherproject
project. The - a
shortcut is used to append to the
destination table.
bq cp -a mydataset.mytable myotherproject:myotherdataset.mytable
API
You can copy an existing table through the API by calling the
bigquery.jobs.insert
method, and configuring a copy
job. Specify your location in
the location
property in the jobReference
section of the
job resource.
You must specify the following values in your job configuration:
"copy": { "sourceTable": { // Required "projectId": string, // Required "datasetId": string, // Required "tableId": string // Required }, "destinationTable": { // Required "projectId": string, // Required "datasetId": string, // Required "tableId": string // Required }, "createDisposition": string, // Optional "writeDisposition": string, // Optional },
Where sourceTable
provides information about the table to be
copied, destinationTable
provides information about the new
table, createDisposition
specifies whether to create the
table if it doesn't exist, and writeDisposition
specifies
whether to overwrite or append to an existing table.
C#
Before trying this sample, follow the C# setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery C# API
reference documentation.
Go
Before trying this sample, follow the Go setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Go API
reference documentation.
Java
Before trying this sample, follow the Java setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Java API
reference documentation.
Node.js
Before trying this sample, follow the Node.js setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Node.js API
reference documentation.
PHP
Before trying this sample, follow the PHP setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery PHP API
reference documentation.
Python
Before trying this sample, follow the Python setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Python API
reference documentation.
Copy multiple source tables
You can copy multiple source tables to a destination table in the following ways:
- Using the
bq
command-line tool'sbq cp
command. - Calling the
jobs.insert
method, configuring acopy
job, and specifying thesourceTables
property. - Using the client libraries.
All source tables must have identical schemas, and only one destination table is allowed.
Source tables must be specified as a comma-separated list. You cannot use wildcards when you copy multiple source tables.
To copy multiple source tables, select one of the following choices:
bq
Issue the bq cp
command and include multiple source tables as a
comma-separated list. Optional flags can be used to control the write
disposition of the destination table:
-a
or--append_table
appends the data from the source tables to an existing table in the destination dataset.-f
or--force
overwrites an existing destination table in the destination dataset and doesn't prompt you for confirmation.-n
or--no_clobber
returns the following error message if the table exists in the destination dataset:Table 'project_id:dataset.table' already exists, skipping.
If-n
is not specified, the default behavior is to prompt you to choose whether to replace the destination table.--destination_kms_key
is the customer-managed Cloud Key Management Service key used to encrypt the destination table.
--destination_kms_key
is not demonstrated here. See
Protecting data with Cloud Key Management Service keys
for more information.
If the source or destination dataset is in a project other than your default
project, add the project ID to the dataset names in the following format:
project_id:dataset
.
(Optional) Supply the --location
flag and set the value to your
location.
bq --location=location cp \ -a -f -n \project_id:dataset.source_table
,project_id:dataset.source_table
\project_id:dataset.destination_table
Replace the following:
location
: the name of your location. The--location
flag is optional. For example, if you are using BigQuery in the Tokyo region, you can set the flag's value toasia-northeast1
. You can set a default value for the location using the.bigqueryrc
file.project_id
: your project ID.dataset
: the name of the source or destination dataset.source_table
: the table that you're copying.destination_table
: the name of the table in the destination dataset.
Examples:
To copy the mydataset.mytable
table and the mydataset.mytable2
table to
mydataset2.tablecopy
table, enter the following command . All datasets are
in your default project.
bq cp \
mydataset.mytable,mydataset.mytable2 \
mydataset2.tablecopy
To copy the mydataset.mytable
table and the mydataset.mytable2
table to
myotherdataset.mytable
table and to overwrite a destination table with the
same name, enter the following command. The destination dataset is in the
myotherproject
project, not your default project. The -f
shortcut is
used to overwrite the destination table without a prompt.
bq cp -f \
mydataset.mytable,mydataset.mytable2 \
myotherproject:myotherdataset.mytable
To copy the myproject:mydataset.mytable
table and the
myproject:mydataset.mytable2
table and to return an error if the
destination dataset contains a table with the same name, enter the following
command. The destination dataset is in the myotherproject
project. The
-n
shortcut is used to prevent overwriting a table with the same name.
bq cp -n \
myproject:mydataset.mytable,myproject:mydataset.mytable2 \
myotherproject:myotherdataset.mytable
To copy the mydataset.mytable
table and the mydataset.mytable2
table and
to append the data to a destination table with the same name, enter the
following command. The source dataset is in your default project. The
destination dataset is in the myotherproject
project. The -a
shortcut is
used to append to the destination table.
bq cp -a \
mydataset.mytable,mydataset.mytable2 \
myotherproject:myotherdataset.mytable
API
To copy multiple tables using the API, call the
jobs.insert
method, configure a table copy
job, and specify the sourceTables
property.
Specify your region in the location
property in the
jobReference
section of the job resource.
Go
Before trying this sample, follow the Go setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Go API
reference documentation.
Java
Before trying this sample, follow the Java setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Java API
reference documentation.
Node.js
Before trying this sample, follow the Node.js setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Node.js API
reference documentation.
Python
Before trying this sample, follow the Python setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Python API
reference documentation.
View current quota usage
You can view your current usage of query, load, extract, or copy jobs by running
an INFORMATION_SCHEMA
query to view metadata about the jobs ran over a
specified time period. You can compare your current usage against the quota
limit to determine your quota usage for a particular type of job. The following
example query uses the INFORMATION_SCHEMA.JOBS
view to list the number of
query, load, extract, and copy jobs by project:
SELECT sum(case when job_type="QUERY" then 1 else 0 end) as QRY_CNT, sum(case when job_type="LOAD" then 1 else 0 end) as LOAD_CNT, sum(case when job_type="EXTRACT" then 1 else 0 end) as EXT_CNT, sum(case when job_type="COPY" then 1 else 0 end) as CPY_CNT FROM `region-eu`.INFORMATION_SCHEMA.JOBS_BY_PROJECT WHERE date(creation_time)= CURRENT_DATE()
To view the quota limits for copy jobs, see Quotas and limits - Copy jobs.
Delete tables
You can delete a table in the following ways:
- Using the Google Cloud console.
- Using a data definition language (DDL)
DROP TABLE
statement. - Using the
bq
command-line toolbq rm
command. - Calling the
tables.delete
API method. - Using the client libraries.
To delete all of the tables in the dataset, delete the dataset.
When you delete a table, any data in the table is also deleted. To automatically delete tables after a specified period of time, set the default table expiration for the dataset or set the expiration time when you create the table.
Required permissions
To delete a table, you need the following IAM permissions:
bigquery.tables.delete
bigquery.tables.get
Each of the following predefined IAM roles includes the permissions that you need in order to delete a table:
roles/bigquery.dataEditor
roles/bigquery.dataOwner
roles/bigquery.admin
Additionally, if you have the bigquery.datasets.create
permission, you can
delete tables of the datasets that you create.
For more information about IAM roles and permissions in BigQuery, see Predefined roles and permissions.
Delete a table
To delete a table:
Console
In the Explorer panel, expand your project and dataset, then select the table.
In the details panel, click Delete table.
Type
"delete"
in the dialog, then click Delete to confirm.
SQL
Use the
DROP TABLE
statement.
The following example deletes a table named mytable
:
In the Google Cloud console, go to the BigQuery page.
In the query editor, enter the following statement:
DROP TABLE mydataset.mytable;
Click
Run.
For more information about how to run queries, see Running interactive queries.
bq
Use the bq rm
command with the --table
flag (or -t
shortcut) to delete
a table. When you use the bq
command-line tool to remove a table, you must confirm the
action. You can use the --force
flag (or -f
shortcut) to skip
confirmation.
If the table is in a dataset in a project other than your default
project, add the project ID to the dataset name in the following format:
project_id:dataset
.
bq rm \ -f \ -t \ project_id:dataset.table
Replace the following:
project_id
: your project IDdataset
: the name of the dataset that contains the tabletable
: the name of the table that you're deleting
Examples:
To delete the mytable
table from the mydataset
dataset, enter the
following command. The mydataset
dataset is in your default project.
bq rm -t mydataset.mytable
To delete the mytable
table from the mydataset
dataset, enter the
following command. The mydataset
dataset is in the myotherproject
project, not your default project.
bq rm -t myotherproject:mydataset.mytable
To delete the mytable
table from the mydataset
dataset, enter the
following command. The mydataset
dataset is in your default project. The
command uses the -f
shortcut to bypass confirmation.
bq rm -f -t mydataset.mytable
API
Call the tables.delete
API method and specify the table to delete using the tableId
parameter.
C#
Before trying this sample, follow the C# setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery C# API
reference documentation.
Go
Before trying this sample, follow the Go setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Go API
reference documentation.
Java
Before trying this sample, follow the Java setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Java API
reference documentation.
Node.js
Before trying this sample, follow the Node.js setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Node.js API
reference documentation.
PHP
Before trying this sample, follow the PHP setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery PHP API
reference documentation.
Python
Before trying this sample, follow the Python setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Python API
reference documentation.
Ruby
Before trying this sample, follow the Ruby setup instructions in the
BigQuery quickstart using
client libraries.
For more information, see the
BigQuery Ruby API
reference documentation.
Restore deleted tables
You can undelete a table within the time travel window specified for the dataset, including explicit deletions and implicit deletions due to table expiration. The ability to configure the time travel window is in preview.
The time travel window can have a duration between two and seven days. After the time travel window has passed, it is not possible to undelete a table using any method, including opening a support ticket.
When you restore a partitioned table that was deleted because it expired, you must manually recreate the partitions.
You can restore a table that was deleted but is still within the time travel
window by copying the table to a new table, using the @<time>
time decorator.
To copy the table, you can use the bq
command-line tool or the client libraries:
Console
You cannot undelete a table by using the Google Cloud console.
bq
To restore a table, use a table copy operation with the @<time>
snapshot
decorator. First, determine a UNIX timestamp of when the table existed
(in milliseconds). Then, use the bq copy
command with the snapshot
decorator.