Snowflake has many advantages:
Please share your migration tips with us.
You can select two types of loading the table into your workspace - Copy Table and Clone Table.
Copy Table is the default option and it physically copies the table from our storage to your workspace. Using Copy Table allows you to refine the input mapping using various filters.
Clone Table avoids physical transfer of the data and clones the table from storage without any processing.
By switching Load Type to Clone Table the input mapping will utilize the Snowflake
CLONE command has no further options all other input mapping options will be disabled
(except for Source and Destination of course).
Clone Table is useful when
CLONE command will execute the input mapping almost instantly for a table of any size (typically under 10 seconds)
as it physically does not move any data.
Table loaded using Clone Table will contain all columns of the original table and a new
This column is used internally by Keboola Connection to compare with the value of the Changed in last filter.
The value in the column contains a unix timestamp of the last change of the row which is
You can use this column to set up incremental processing.
Unlike Redshift or MySQL, Snowflake is case sensitive. All unquoted table/column names are converted to upper case while quoted names keep their case.
So if you want to create the following table,
all of these commands will work
while this one will not:
Be especially careful when setting up input and output mappings.
When writing your transformation script, quoting all table and column names is required. Snowflake converts all unquoted table/column identifiers to uppercase, which won’t match table/column identifiers created by Keboola Connection.
By default, Snowflake uses the
YYYY-MM-DD HH24:MI:SS.FF3 format
when converting the timestamp column to a character string.
This means that if you create a table in a transformation which uses a
the table value will come out as
2018-04-09 06:43:57.866 -0700 in Storage. If you
want to output it in a different format, you have to cast the column to a string first, for example:
Do not use
ALTER SESSION queries to modify the default timestamp format, as the loading and unloading sessions are separate from your transformation/sandbox session and the format may change unexpectedly.
DY, DD MON YYYY HH24:MI:SS TZHTZM
Important: Snowflake works with time zones (and Daylight Savings Time), requiring you to distinguish between various conversion functions: