Property | Description |
---|---|
Encoding | Type of encoding to use with source and target files. The default value is OEM. |
SQL Output | Output mode for SQL statements. There are four output modes: • Target Only (default) - Uses bound mode, which uses bind variables. SQL statements are sent to the Target and not to the SQL log specified in the SQL Log property. • Target Only (Unbound mode) - Uses unbound mode, which 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 specified in the SQL Log property. • Target and SQL Log - Sends SQL statements to the Target and to the SQL log specified in the SQL Log property. • SQL Log Only - Sends SQL statements only to the SQL log file specified in the SQL Log property. Note: Bound mode is faster since bind variables are used. |
SQL Log | SQL log file in the default installation directory. The default file name is sql.log. 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 | If set to true, null values are sent to the database when inserting or updating records. If set to false, null values are not sent to the database when inserting or updating records. Also, this property forces the connector to operate in unbound mode, which may cause slower performance. The default value is false. 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 | If set to true, allows you to see all tables created by the Database Administrator (DBA) in the database. The system table names appear in the table list. The default value is false. Note: This property is applicable only if you have logged in to the database as the DBA. Only the DBA has access to system tables. |
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 | 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 the changes after they are done. The default value is false. |
IdentifierQuotes | Quoted identifiers are used to parse the SQL statement 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: SELECT * FROM "Accounts Receivable" 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 four options: • Default • None • " • ' |
MaxDataLength | 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 | Allows you to specify an isolation level when reading from or writing to a database table with ODBC. The isolation levels are: • 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 P1, P2 or P3. 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. |
ArraySize | Determines the number of rows to be sent to the server at a 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 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. |
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. |
Use Unicode Driver | Specify whether a unicode driver must be used for connecting to Actian Zen. The options available are: • True • False False is the default value. |