Property | Description |
|---|---|
Encoding | Type of character encoding to use with source and target files. The default value is OEM. 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. Note: This property is not encoding of the database that you connect to, but it is the encoding in which the connector expects to receive SQL query statements that must be sent to the database. |
ConstarintDDL | Additional SQL data definition language statements that must be executed after the target table is created. This is similar to the support provided for SQL pass-through in the SQL import connectors. Each line must be a valid ODBC DDL statement. For example, you can have the following statements: CREATE UNIQUE INDEX index1 ON mytable (Field1 ASC) CREATE INDEX index2 ON mytable (Field2, Field3) These statements create two indices on the table mytable. The first statement does not allow duplicates and the index values are stored in ascending order. The second index is a compound index on fields Field2 and Field3. The ConstraintDDL is run only if the output mode is Replace for the target. If there are any errors, they are written to the error and event log file. An error during transformation displays the Transformation Error dialog. You can ignore the DDL errors and continue the transformation. ConstraintDDL also supports an escaping mechanism that allows you to specify DDL in the native SQL of the DBMS. Any statement preceded by an @ sign is sent directly to DBMS. The following is a DDL statement for creating a primary key for the table mytable: @CREATE INDEX pk_mytable ON mytable (Field1, Field2) WITH PRIMARY Some ODBC drivers do not support the SQL extensions required to create a primary key with the ODBC variant of the SQL CREATE statement. In these cases, to create primary keys, use native SQL. |
CommitFrequency | Allows you to control how often data is committed to the database when the AutoCommit property is set to False. The default value is zero that is, the data is committed at the end of the transformation, allowing rollback on error. This is the slowest setting. When performing large transformations, this is not practical as it may produce too many transaction log entries. Specifying a nonzero value indicates that data is committed to the database after inserting or updating specified number of records. |
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. |
IdentifyInsert | Determines if the integration platform automatically inserts Identity fields into your database. The default is False. If you want to allow Identity fields, you must change this property to true. |