Property | S/T | Description |
|---|---|---|
Encoding | S/T | Sets the character encoding for ODBC 3.x source and target files. Note: Shift-JIS encoding is used only in Japanese operating systems. UCS-2 is no longer considered a valid encoding name, but you may use UCS2. In the data file, change UCS-2 to UCS2. This property is not the encoding of the database that you connect to, but it is the encoding in which the connector expects to receive SQL query statements to be sent to the database. |
ServerLocale | S/T | Specifies the database connection for the server. This property has three values, • EN_US.819: This is the default value for the Informix database. • EN_US.UTF8: This value is used to support UNICODE data. • Custom: This is the value for the DB_LOCALE variable which you set when creating the database. |
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: CREATE UNIQUE INDEX index1 ON mytable (Field1 ASC) CREATE INDEX index2 ON mytable (Field2, Field3) 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. 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: @CREATE INDEX pk_mytable ON mytable (Field1, Field2) WITH PRIMARY 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 | Allows users to specify the number of records to insert or update before issuing a commit to the database. This property is applicable only if the AutoCommit property is set to FALSE. 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. |
AutoCommit | T | If set to True, it allows you to automatically commit changes as they are made by each SQL statement, instead of waiting until the end of the transaction. Also, if this option is set to True, you cannot roll back changes after they are done. It will overwrite the CommitFrequency value, which means that the changes are committed by each SQL statement irrespective of the value set for CommitFrequency. The default value is False. |
BulkOperations | T | Specify whether or not to instruct the integration platform to use bulk operations for faster insert. If set to true, an insert statement or bulk add is executed for each record. This allows you to maximize speed. The default is false, the slower setting. |
WhereStmt | S | Provides a pass-through mechanism for SQL connectors where advanced users can construct the Where clause of the SQL query themselves. It can be used as an alternative to writing a lengthy query statement. You may use this to instruct the SQL database server to filter the data based on a particular condition before sending it to the integration platform. There is no default value for this property. Note: This property is not applicable when the source connection is a query statement or file. This property enables data filtering when you select a table. |
SystemTables | S/T | The SystemTables property is only applicable if you are logged onto the database as the database administrator. Only the DBA has access to SystemTables. If set to true, this property allows you to see all the tables created by the DBA. The system table names appear in the table list. The default is false. |
Views | S/T | If set to True, this property allows you to see the view names in the table list along with the table names. Default is True. Note: This property supports only Append and DeleteAndAppend output modes and does not support the Replace output mode. |
CursorType | S | The type of cursor to use for retrieving records from the source table. The choices available are Forward Only, Static and Dynamic. The default setting is Forward Only. For more information, see Cursors. |
PrimaryKey | T | Specify a list of field names used to create a primary key. Field names are delimited by commas. If this property contains one or more field names, these names are included in the SQL CREATE statement when the connector is in Replace mode. This property has no default. To use this property, your ODBC driver must support integrity enhancement facility (IEF). Only the more advanced ODBC drivers support this. |
UseCursors | T | The UseCursors property allows you to turn cursor support on or off. The default is false. If set to true and the specified ODBC driver does not support cursor inserts, the integration platform uses the SQL INSERT mode of adding records. For exports, cursor support is supposed to enhance the performance of inserting records. This appears to be the case for desktop databases. For database servers, there is no noticeable change in insert speed. They seem to execute prepared queries about as quickly as they handle cursor inserts Another complication of cursor inserts is that some drivers require that the target table be indexed, otherwise positioned updates (cursors) are not allowed. Two additional properties in the ODBC export connector address this issue: PrimaryKey and ConstraintDDL. |
ArraySize | T | Determines the number of rows to be sent to the server at one time. The default value is 1000. Larger values will buffer multiple rows and send them all at once. While this improves the speed, it affects error reporting (a server error won't be detected/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 the value to be set that high, 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 ignored and a message is logged indicating this condition. |
IdentifierQuotes | S/T | All databases have what are called quoted identifiers. You use quoted identifiers to make the SQL statement parseable and distinguish between columns and character data in SQL statements. For example, Oracle uses double quotes for column and table names in SQL statements and uses single quotes for character data. In a SQL statement, you should 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: SELECT * FROM "Accounts Receivable" If you do not use identifier quotes, the parser assumes there are two tables, Accounts and Receivable, and returns a syntax error that they are not separated by a comma. \ If either of the following values contain a space, set the identifierQuotes property on the source and the target to ““ or Default: • the value of the source connector part Table/View field. • the value of a source column name (for example, Account Number). Otherwise, if the IdentifierQuotes property is set to None, a SQL error is returned and the source table data is not displayed. IdentifierQuotes has the following options: • Default • None • " |
MaxDataLength | S/T | The maximum data length for long data types. The default is 1 MB. You can reset this number as you choose based on your available memory capabilities and Target requirements. Some ODBC drivers have limitations concerning the maximum data length they can handle. If you choose an Application (ODBC) source or target connector and the default setting is not 1 MB, the integration platform presets the default for the capabilities of that particular ODBC driver. It is not recommended that the MaxDataLength property be set any higher under those conditions. |
TransactionIsolation | S/T | The Translation Isolation option allows you to specify any one of five different isolation levels when reading from or writing to a database table with ODBC. 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). The following lists the four supported isolation levels. • READ_UNCOMMITTED – Permits P1, P2, and P3. • READ_COMMITTED – Permits P2 and P3. Does not permit P1. • REPEATABLE_READ – Permits P3. Does not permit P1 and P2. • SERIALIZABLE – (Default) Does not permit any of P1, P2, and P3. For further details about TransactionIsolation levels, see the Microsoft ODBC SDK documentation. Note: When performing Join or Look up operation with the Source, Join, and Target using the same HCL Informix connector, the Transaction Isolation property value on Join or Lookup should be set to any value other than the default value SERIALIZABLE. |
StripLeadingBlanks | S/T | Strips out leading blanks in all data fields if set to true. Default is false. Note: This property is applied to the source connector only if Source Table/View is set to Table/View. It is not applied if Source Table/View is set to Query Statement or Query Files. |
StripTrailingBlanks | S/T | Strips out trailing blanks in all data fields if set to true. Default is false. Note: This property is applied to the source connector only if Source Table/View is set to Table/View. It is not applied if Source Table/View is set to Query Statement or Query Files. |