Welcome Guest! Log in

This article describes the principal changes of Specific 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.




A new parameter named 'Delete Previous Rejects' has been added to allow managing the deletion of previous rejects.

Refer to parameter documentation for further information.



LOAD File to Sybase IQ

A new Template offering the possibility to load data from a database into Sybase IQ using Sybase's specific loader is now available!

Using "LOAD TABLE" statement, the new "LOAD File to Sybase IQ" Template allows to optimize the loading step through the use of specific loader.

Refer to Template and parameters documentation for further information.




Creation of pre-integration and reject tables is now performed with same charset as the one defined in Metadata for target table.

This helps to fix issues when working with tables with different charset than default database charset.

Note that table charset attribute can be defined and reversed in table Metadata from Designer S19.0.18 and higher, which is therefore the prerequisites to benefit of this modification.



Drop of temporary integration objects fixed

Step which drops the integration table created during integration was not executed because of an incorrect link condition.

This has been fixed and this drop step is now correctly executed at the end of the integration.



Recycling of previous rejects fixed

When using the option to recycle the rejects of previous execution on Integration Templates 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.

Those issues were existing in multiple Integration Templates which have all been fixed.



LOAD XML to Oracle (with SQL Loader)

A new Oracle specific Template has been added to perform data loading from an XML file to Oracle using SQL*Loader.

Offering better performances than standard XML loading, this Template also supports loading multiple sources XML files at the same time, which will each be loaded in a dedicated SQL*Loader execution.



INTEGRATION File (Mssql Export with BCP)

This new Microsoft SQL Server specific Template has been added to export data from a Microsoft SQL Server table into a file using BCP utility.

When exporting data from Microsoft SQL Server into a file in a Mapping, simply select this Template for performing the export using BCP, which offers better performances when working with large set of data.

For further information do not hesitate to consult the Template's documentation.


LOAD File to Mssql / INTEGRATION File to Mssql

These two Templates, which were using Microsoft SQL Server BULK statement, has been updated to also support using the BCP utility.

New parameters have been added to define which method should be used.



Oracle Reject Template has been updated to offer better performances on Alternate Keys (AK) controls.



Column comparison modified for ntext and image datatypes

All the queries performing columns comparison have been updated to take into account the particularities of columns of "ntext" and "image" datatypes.

These datatypes require the comparison to be done with the 'LIKE' operator instead of the '=' one.

When using those columns, the comparisons in the Template were not correct as they were using the '=' operator.

Queries which perform column comparison will now use 'LIKE' keywork when working with "ntext" and "image" datatypes.



When defining "Deletion Strategy" parameter to "all rows" in a Mapping, all incremental update steps will not be performed anymore by the Template.

They will be automatically disabled and not executed when using this option as there will never be any updates to perform.

As a reminder this option is used to remove all rows from target table before processing.



LOAD File to Oracle (with Loader)

When using external table mode, the create table statement for the external table now computes the size of source fields and then specifies it if needed in the statement.

The size is retrieved from the source file Metadata and is specified when it exceed 255 (the default value Oracle is using for fields in external table when no size is specified.)

This allows to load files with large fields.



New parameters to configure the transactional mode used for operations on work table and target table

Two parameters have been added to choose the transactional mode that should be used by the Templates when performing operations on work tables and target tables:

'Transactional Mode On Work Tables' and 'Transactional Mode On Target'

The mode used on each action inside the Template has been revised to be more consistent, as some actions were not in the same mode between each other.


New parameter to add options on the work table creation statement

A new parameter called 'Work Table Option' has been added, which offers the possibility to add additional options on the crate table statement of the work tables.

It can be helpful for specifying the 'NOT LOGGED INITIALLY' option for instance, which reduce all the logging performed by DB2-UDB when doing operations on the work tables.



INTEGRATION File to Mssql (with BULK) and LOAD File to Mssql (with BULK).proc

When using the dynamic method to load the file, the automatic calculation of columns based on the file's header was not using the row separator, field separator, and charset defined in the File Metadata.

This issue has been fixed and the steps calculating the columns will now use those when reading the file's header.



A new REJECT Mssql Template has been added with the Microsoft SQL Server Templates.

This template handles the Microsoft SQL Server specificities, such as using the fully qualified name for the columns, and supporting having delimiters around the index name.



INTEGRATION File to Mssql (with BULK)

A new INTEGRATION File to Mssql (with BULK) Template has been added with the Microsoft SQL Server Templates.

This Template offers the possibility to BULK load a file directly into a target table without going through temporary work objects.

This can be useful on situations where there is no need for transformations, rejects or updates detection.


INTEGRATION Sybase IQ with Slowly Changing Dimension

Several issues on the Sybase Template dedicated to Slowly Changing Dimension has been fixed.

There were some situations where the generated queries were incorrect such as when having only columns with historizedIfModfied mode, or only with updateIfModfied mode.

There were also actions unexpectedly executed in situations when it was not necessary.

All those behaviors have been fixed in this updated version.




All the queries performing columns comparison have been updated to take into account the particularities of columns of "text" datatype.

The text datatype, which has been defined has deprecated by Microsoft requires the comparison to be done with the 'LIKE' operator instead of the '=' one.

When using those columns, the comparisons in the Template were not correct as they were using the '=' operator.

This has been fixed and the comparisons now acts differently for columns of type "text".


LOAD File to Mssql (with BULK)

This template has been updated to support loading files from which columns order and number can vary between each file.

A new parameter called File format Method has been added for the user to be allowed to change how the SQL Server format file containing the list of columns to load should be calculated.

This parameter supports two values:

  • 'from_metadata' which corresponds to the method previously used by the Template which calculates at the generation of the delivery the columns to load based on the source File Metadata
  • 'from_file_dynamic' which corresponds to the new method calculating automatically at the execution of the delivery the columns order and number based on the file itself

The new method allows to load files from which the columns may not always be at the same position and which can contain additional columns.

The template will dynamically find the columns order from the first line of the file which is expected to be the header of the file containing the columns list.

This will then be used to generate the correct format file with the correct column order, ignoring the additional columns which are not originally in the source Metadata.

This method is supported for delimited files only.


Informix Templates moved to a standalone package

The Informix Templates which were previously shipped with the Specific Templates package have been separated in their own package for clarity.

You can now find them in their own package in the Template's download page, and find their release notes at this page.




The way alternate keys (unique constraints) are verified while using the Oracle Reject template has been updated to match exactly the rules defined in Oracle reference documentation.

Most notably for the detection and handling of null values in the columns of the constraint.

For instance, when two rows have identical data for the columns of the constraint and one of those columns contains a null value in both rows, the rows are now correctly rejected, as null values are not considered to satisfy uniqueness except when all the columns of the constraint are null.

Refer to the Oracle documentation and documentation of the Template for further information.



You have no rights to post comments


Suggest a new Article!