Property | Description |
|---|---|
Encoding | 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 | 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. |
SQL Output | Allows you to specify bound or unbound mode and whether or not to write SQL statements to a SQL log. Keep in mind that bound mode is faster, as bind variables are used. Select from the following: • Target Only (default) - Use bound mode, which uses bind variables. SQL statements are sent to the target only. • Target Only (Unbound Mode) - Use unbound mode. Does not use bind variables and sends the literal SQL statement to the database engine. SQL statements are sent to the target and not to the SQL log file specified in the SQL Log property. • Target and SQL Log - Sends SQL statements to the target and the SQL log file specified in the SQL Log property. • SQL Log Only - Sends SQL statements only to the SQL log file specified in the SQL Log property. |
SQL Log | SQL log file. The default is sql.log in the default installation directory. To use a different log, browse to the file, or enter the path and file name. Note: SQL statements are sent to the SQL Log file only if the SQL Output property is set to either Target and SQL Log or SQL Log Only. |
UpdateNullFields | Null values are sent to the database when inserting or updating records. The default is true. If you select false, null values are not sent to the database when you insert or update records. This forces the connector to operate in unbound mode, which may cause slower performance. Best Practice — If fields in the target record are not mapped, then the null values are passed to the target. If you do not want to write to these fields, then it is recommended to set the value for UpdateNullFields to False. |
SystemTables | 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 | 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. |
AutoCommit | 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. The default value is False. |
IdentifierQuotes | 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 | 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 | 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 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). 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 – 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. |
ArraySize | 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. |
StripLeadingBlanks | Strips out leading blanks in all data fields if set to true. Default is false. |
StripTrailingBlanks | Strips out trailing blanks in all data fields if set to true. Default is false. |