This article describes the principal changes of Snowflake Templates.
The Template download section can be found at this page
Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.
If you have any question, any feature request or any issue, do not hesitate to contact us.
Ability to customize and manage compression behavior
A whole new mechanism has been added to provide the ability to customize how compression is managed when loading data into Snowflake.
New parameters have been added in Metadata to define the default compression strategy which should be used when loading data, which can also be overridden on each Mapping through corresponding new parameters in Templates.
For further information, refer to getting started article which has been updated with more details about compression.
Ability to choose load method
A new parameter named 'Load Method' has been added in Load Templates, which is used to define how loading should be performed.
Two methods are available for now, "insert" and "copy", which correspond to the type of SQL Query used for loading data.
Depending on chosen method, an insert or a copy statement will be used.
New parameters to adjust loading behaviors
A bunch of new parameters have also been added on Load Templates to adjust more precisely loading behaviors: "Escape Unenclosed Field", "No File Behavior", "Work Folder", "Time Format", "Timestamp Format".
Refer to their documentation for further information.
Loading of files improved to be the closest possible to source file Metadata
When loading a source file into Snowflake, generated queries and temporary objects have been improved to be the closest possible to source file Metadata.
More options of source file Metadata are retrieved and computed to generate corresponding options and format on queries, to be sure loading will be efficient and matching.
Multiple issues have been fixed in this new version.
Refer to the history section of each Template for further information.
Incorrect datatype generated in temproary tables when using NUMBER datatype
Datatype used in temporary tables for NUMBER columns was incorrectly generated as INT instead of NUMBER.
NUMBER datatype creation mask has been updated to generate correct syntax.
Recycling of previous rejects fixed
When using the option to recycle the rejects of previous execution an extra step is executed to add those previous rejects in the integration flow.
This step had several issues which avoided it to work properly and which have been fixed in this version.
Moreover, possible duplicates while retrieving those rejects are now filtered using DISTINCT keyword.