Identifier differences between BigQuery and Snowflake
This page shows the differences between identifier types in BigQuery and Snowflake
Quoted identifiers
BigQuery quoted identifiers are enclosed by backticks (`) while Snowflake encloses them in double quotes (“).
In BigQuery, quoted identifiers stick to the case sensitivity rules, which means that, for example, column names are still case insensitive even when quoted:
BigQuery
In Snowflake, case sensitivity of quoted identifiers depends on the session parameter QUOTED_IDENTIFIERS_IGNORE_CASE, by default quoted identifiers comparison is case sensitive, this means that the result code from migrating the above example:
Snowflake
Will fail when executing the second select unless the session parameter is set to TRUE.
How SnowConvert migrates quoted identifiers
SnowConvert will analyze quoted identifiers to determine if they contain non-alphanumeric characters or are reserved words in Snowflake, if they do then it will transform them to quoted identifiers in Snowflake, alphanumeric identifiers will be left unquoted:
BigQuery
Snowflake
Known issues
Quoted identifiers
In Big Query, the following identifiers are equivalent:
BigQuery
But SnowConvert will mark the second insert statement with MSCEWI1050, this happens because test.`MyTable
Ș1`
and `test.MyTable
Ș1`
are processed as two different objects names, therefore the definition of `test.MyTable#1` is considered as a missing reference:
Snowflake
This missing reference case will not affect the identifiers transformation, both identifiers will be transformed correctly and match the resulting table name, however, it may affect the transformation of statements that require semantic information about the objects being referenced. To avoid missing reference warnings or incomplete statement transformations due to this issue please consider changing the usages of quoted identifiers so they are consistent with the name used to create the object in the input code.
Unquoted identifiers
By default, BigQuery considers table and dataset names as case insensitive, unless the is_case_sensitive option is activated for the dataset, this allows the following tables to coexist without problems:
BigQuery
However, unquoted identifiers in Snowflake are always stored and compared in uppercase, meaning that test.MyTable
will raise a duplicated object error when trying to create it. SnowConvert also works under the assumption that identifiers are case insensitive, so when one of these scenarios appears during transformation, MSCEWI1039 will be generated to warn the user:
Snowflake
Last updated