User Guide > Map Connectors > Source and Target Map Connectors > ODBC 3.5 Multimode
Was this helpful?
ODBC 3.5 Multimode
In most cases, the integration platform connects to the file formats you are using either directly through knowledge of their physical file formats (for example, ASCII, Lotus, xBASE...), or through the native interfaces supplied by those vendors who define a particular data format such as Oracle. ODBC provides another method (and sometimes the only method) for connecting to a particular file format. The ODBC 3.5 Multimode connector allows you to perform multiple operations (such as table drops and table inserts) directly on your target database.
Note:  This connector only supports 64-bit ODBC drivers.
The integration platform can write to ODBC 3.5 Multimode format as target type. It is not available as a source type.
Tip...  This connector is designed for Unicode data sets. If your data is not Unicode, use the ODBC 3.x Multimode connector. See ODBC 3.x Multimode.
Connectivity Pointers
• On the surface, it may appear that this connector would allow you to make a connection to any Source that has an ODBC driver. However, for transformations written with this connector to work, your target format must support SQL statements.
• As a general rule, when connecting to a database with ODBC, most applications require the database engine to be up and running at the time the connection is attempted.
Connector-Specific Notes
Target Schema modification: In multimode targets, modifications to column names, data types, and sizes are not permitted.
Query Statement Support: Your target format must be able to support SQL statements for you access multiple tables in the same transformation, each time that transformation runs written with this connector to work, such as Oracle and SQL Server.
Auto-Increment Fields: If your target table contains an auto-increment column, you may get an error at run time. If this occurs, you must delete the field that is causing the problem from the record.
SQL Server: The use of Regional settings in ODBC DSN connections to SQL Server databases is not supported in this release. In order for currency, numbers, dates and times to be interpreted correctly, ensure that the Use regional settings when outputting currency, numbers, dates and times checkbox in the SQL Server DSN settings is not checked. Then in the ODBC connector DriverOptions property, type Regional=No.
Connector Parts
Connector parts are the fields you configure to connect with a data source or target.
The settings that are available depend on the connector you select.
For a list of all parts for target connectors, see Specifying Connector, Parts, and Properties.
Property Options
You can set the following target properties:
Property
Description
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. 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.
DriverCompletion
Allows you to control whether or not the driver prompts you for information. The options available are Prompt, Complete, Complete Required, No Prompt. The Prompt option prompts the user for every individual bit of information. Complete prompts the user for any information they forgot to enter. The Complete Required option prompts the user only for information that is essential to complete the connection. The No Prompt option does not prompt the user for any information. The default is Complete.
DriverOptions
Enter any valid ODBC connect string options here.
DSNType
Data sources or drivers to connect to in the Data Source Name (DSN) list. DSNs are listed in Control Panel > Administrative Tools > ODBC Data Source Administrator window. The options are:
• User: Created for a specific user. DSN information is stored in the registry.
• System: Can be used by anyone who has access to the machine. DSN information is stored in the registry.
• User & System: This is the default option.
For more information, see Configuring ODBC Data Source.
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 return a syntax error that they are not separated by a comma.
IdentifierQuotes has four 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, then the integration platform sets 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.
ModifyDriverOptions
Allows you to store the ODBC connection. The default is true. If you set this to false, you are prompted for your connection information each time that you run your you access multiple tables in the same transformation, each time that transformation runs.
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.
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.
Synonyms
If set to true, this property allows you to see synonyms. The alias names appear in the table list along with the tables. Default is 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.
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.
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.
Encoding
Sets the character encoding for ODBC 3.5 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.
Supported Data Types
The only available data type is Text.
Note:  For ODBC 3.5 using a DB2 DSN, column sizes for text-type fields (char, varchar, etc.) should be specified in bytes, not characters. This is important when sending Unicode that contains characters outside the regular ASCII range. The strings are encoded using UTF-8, and the column width needs to be specified as the (max) number of bytes that will occur in the UTF-8 string.
Length
These are field lengths in your data. If you need to change field lengths, reset them in the schema.
Last modified date: 02/01/2024