Encoding

ST

Type of encoding to use with source and target files. The default value is OEM.

WhereStmt

S

Provides a pass-through mechanism for SQL connectors where advanced users can construct the Where clause of the SQL query. It is also used as an alternative to writing lengthy query statements in the Query Statement text box. You can use the Where statement to instruct the SQL database server to filter the data based on a condition before it is sent to the integration platform. Omit Where when you enter the clause.

SystemTables

ST

If set to True, allows you to see all tables created by the DBA in the database. The system table names appear in the table list. The default value is False.

Views

ST

If set to true (default), allows you to see views. View names appear in the table list along with table names.

CursorType

S

Type of cursor to use for retrieving records from the source table. The options available are:

The default value is Forward Only.

IdentifierQuotes

ST

Quoted identifiers are used to make the SQL statement parseable and distinguish between columns and character data in SQL statements. All databases have quoted identifiers.

In a SQL statement, you must enclose identifiers containing special characters or match keywords in identifier quote characters; (also known as delimited identifiers in SQL-92). For example, the Accounts Receivable identifier is quoted in the following SELECT statement:

If you do not use identifier quotes, the parser assumes there are two tables, Accounts and Receivable and return a syntax error that they are not separated by a comma.

IdentifierQuotes has three options:

MaxDataLength

ST

Maximum number of characters to write to a field. It is the maximum data length for long data types. The default value is 1 MB. You can change this value based on the available memory and target requirements.

When this connector requests the column field size for these data types, it checks for a returned value greater than the MaxDataLength value. If the value is greater, then the MaxDataLength value is used.

Some ODBC drivers have maximum data length limitations. If you choose an ODBC source or target connector and the default setting is not 1 MB, the integration platform sets the value for that particular ODBC driver. In this case, do not set the MaxDataLength property to a higher value.

TransactionIsolation

ST

Allows you to specify an isolation level when reading from or writing to a database table with ODBC. The isolation levels are:

The default is serializable.

The ANSI SQL 2 standard defines three specific ways in which serializability of a transaction may be violated: P1 (Dirty Read), P2 (Nonrepeatable Read), and P3 (Phantoms).

For further details about TransactionIsolation levels, see the IBM DB2 Universal Database ODBC documentation.

ConstraintDDL

T

Additional SQL data definition language statements that must be executed after the target table is created. This is similar to the support provided for SQL pass-through in the SQL import connectors. Each line must be a valid ODBC DDL statement.

For example, you can have the following statements:

These statements creates two indices on the table mytable. The first statement does not allow duplicates and the index values are stored in ascending order. The second index is a compound index on fields Field2 and Field3.

The ConstraintDDL is run only if the output mode is Replace for the target. If there are any errors, they are written to the error and event log file. An error during transformation displays the Transformation Error dialog box. You can ignore the DDL errors and continue the transformation.

ConstraintDDL also supports an escaping mechanism that allows you to specify DDL in the native SQL of the DBMS. Any statement preceded by an @ sign is sent directly to DBMS.

The following is a DDL statement for creating a primary key for the table mytable:

Some ODBC drivers do not support the SQL extensions required to create a primary key with the ODBC variant of the SQL CREATE statement. In these cases, to create primary keys, use native SQL.

CommitFrequency

T

Controls how often data is committed to the database. The default value is zero that is, the data is committed at the end of the transformation, allowing rollback on error. This is the slowest setting. When performing large transformations, this is not practical as it may produce too many transaction log entries.

Specifying a nonzero value indicates that data is committed to the database after inserting or updating specified number of records.

AutoCommit

T

Automatically commit changes as they are made by each SQL statement, instead of waiting until the end of the transaction. If this option is set to True, you cannot roll back changes after they are done. The default value is False.

BulkOperations

T

Determines if an insert statement is run for each record or a bulk add is executed for each record. The default is False, the slower setting. If you want to maximize speed and instruct the integration platform to use a bulk add, change this setting to True. Use bulk operations for faster insert.

PrimaryKey

T

List of field names that are used to create the primary key. Field names are delimited by commas.

If the PrimaryKey property contains one or more field names, these names are included in the SQL CREATE statement when the connector is in Replace mode.

To use the PrimaryKey property, the ODBC driver must support Integrity Enhancement Facility (IEF). Only advanced ODBC drivers support this.

UseCursors

T

If set to True and the specified ODBC driver does not support cursor inserts, the integration platform falls back on the SQL INSERT mode of adding records. The default value is False.

For exports, cursor support is meant to enhance the performance of inserting records. This is applicable for desktop databases.

For database servers, there is no noticeable change in insert speed. Another complication of cursor inserts is that some drivers require the target table be indexed, otherwise positioned updates (cursors) are not allowed. The PrimaryKey and ConstraintDDL properties in the ODBC export connector addresses this issue.

ArraySize

 

Determines the number of rows to be sent to the server at a time. The default value is 1 and indicates each row is individually sent to the server. Larger values will buffer multiple rows and send them all at once. While this improves the speed, it affects error reporting (a server error will not be detected or reported until the next batch of records is sent to the server).

The maximum value allowed for this property is 100000. While the connector allows a high value to be set, many drivers have lower limits. The connector will log a message indicating if the driver is forcing a lower value for the array size. In addition, the connector does not support arrays when there is a LOB-type field in the table, or when the (maximum) length of a character-type field is longer than 32767 characters. In these cases, a message will be logged indicating the array size has been reduced to 1.

Due to the way the connector attempts to support older drivers, the array support requires BulkOperations and UseCursors is set to True or both must be set to False. If BulkOperations is False and UseCursors is True, then the array size is reset to 1 and a message logged indicating this condition occurred.