Property | Description |
|---|---|
Autocommit | Allows automatic commitment of changes as they are made by each SQL statement, instead of waiting until the end of the transaction. If set to true, you cannot roll back changes. Default is false. |
Encoding | Character encoding used with XML source and target files. Note: Shift-JIS encoding is used only in Japanese operating systems. UCS-2 is no longer a valid encoding name, but you may use UCS2 by changing the string value in the XML file. Default is OEM. |
MaxDataLength | Maximum data length for long data types. Default is 1 MB. You can reset this number based on available memory 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 in respect for the capabilities of that particular ODBC driver, and it is not recommended to set MaxDataLength any higher. Default is 1048576 |
SQL Log | 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. |
SQL Output | Allows you to select bound or unbound mode and whether you want to write SQL statements to a SQL log or not. Keep in mind that bound mode is faster, since bind variables are used. • 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. |
SystemTables | If set to true, this property allows you to see all tables created by the DBA in the database. The system table names appear in the table list. Default is false. Note: This property is applicable only if the user is logged onto the database as the database administrator. Only the DBA has access to system tables. |
Transactionisolation | Allows setting of the transaction isolation level for reading or writing tables. 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 isolation levels are supported. Default is Serializable. • 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 more information, see the Microsoft ODBC SDK documentation. |
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. When set to false, this property 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. |
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. |
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 • " • ‘ |