Property | Use |
|---|---|
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. |
AutoCommit | Allows you to automatically commit changes as they are made by each SQL statement, instead of waiting until the end of the transaction. If AutoCommit is set to true, you cannot roll back changes once they have been made. Default is false. |
DriverCompletion | Allows you to control the driver prompt for information. The options are Prompt, Complete (default), Complete Required, and No Prompt. • Prompt option: Asks the user all information. • Complete option: Asks the user for information they forgot to enter. • Complete Required option: Asks the user only for information required to complete the connection. • No Prompt option: Does not ask the user for information. |
DriverOptions | Specify a valid ODBC driver string connection. The default is empty for a new map. This property can be specified or edited when one of the following is true: • The Source Data Source" is selected and the DSNType is set to "Driver". • All source connection parts are specified and the map is connected to the data. In this case, the connector builds the DriverOptions for you based on the connection parts you enter. Users can edit the pre-built options string as needed. |
Encoding | Allows you to select the type of encoding used with your target file. |
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 • " |
MaxDataLength | Specifies the maximum number of characters to write to a field. The maximum data length for long data types. Default is 1 MB. Reset this number based upon your available memory and target requirements. 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. Under those conditions, do not set the MaxDataLength property to a higher value. |
ModifyDriverOptions | Allows you to store the ODBC connection. Default is true. If you select false, you are prompted for connection information each time you run the transformation. |
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 | 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. |
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 you to specify an isolation level to use 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 isolation levels: • read_uncommitted – Permits P1, P2, and P3. For further details about TransactionIsolation levels, refer to IBM DB2 database ODBC documentation. • 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. For further details about TransactionIsolation levels, refer to 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. 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. |
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. |
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. |