Rules for new datasets

These settings define how managed SQL datasets are mapped to database tables. These settings are applied when creating a new managed SQL dataset. You can always modify these afterwards in the SQL dataset settings. They are also used to create temporary tables if the connection is used for bundled data. See for more information.

Managed datasets will be created in this catalog. You may reference variables here, they will be expanded dynamically
Managed datasets will be created in this database. You may reference variables here, they will be expanded dynamically
Managed datasets will be created in this BigQuery project. You may reference variables here, they will be expanded dynamically
Managed datasets will be created in this schema. You may reference variables here, they will be expanded dynamically
Managed datasets will be created in this BigQuery dataset. You may reference variables here, they will be expanded dynamically
Table name for new managed datasets will be prefixed by this. You may reference variables here, they will be expanded dynamically
Table name for new managed datasets will be suffixed by this. You may reference variables here, they will be expanded dynamically
Table and schema name do not include any variable reference. Datasets will be created with absolute names, which is not recommended for relocation purposes and may cause name clashes.

Date settings

Default “assumed time zone” selection when adding a dataset through this connection. This will be the default timezone assigned to timezone-less data when read in as a DSS datetime with tz.
Default “assumed time zone” selection when performing operations on the Teradata engine, which uses different time zone names. This will be the default timezone assigned to timezone-less data when read in as DSS datetime with tz.

Custom properties

For specific use cases