Keyword | Short Version |
|---|---|
driver | driver |
dsn | dsn |
filedsn | filedsn |
uid | uid |
database | db |
host | host |
pwd | pwd |
server | srvr |
service | serv |
protocol | pro |
client_locale | cloc |
db_locale | dloc |
translationdll | tdll |
translationoption | topt |
connectdatabase | condb |
exclusive | xcl |
cursorbehavior | curb |
savefile | savefile |
options | opt |
description | desc |
enablescrollablecursors | scur |
enableinsertcursors | icur |
optimizeautocommit | oac |
optofc | optofc |
needodbctypesonly | odtyp |
reportkeysetcursors | rkc |
fetchbuffersize | fbc |
describedecimalfloatpoint | ddfp |
donotuselvarchar | dnl |
reportcharcolaswidecharcol | rcwc |
Property | S/T | Description |
|---|---|---|
CursorType | S | The CursorType option specifies the type of cursor to use for fetching records from the source table. The choices are Forward Only, Static, and Dynamic. The default setting is Forward Only. For more information, see Cursors. |
WhereStmt | S | Provides a pass-through mechanism for SQL connectors where advanced users can construct the Where clause of the SQL query themselves. It can be used as an alternative to writing a lengthy query statement. You may use this to instruct the SQL database server to filter the data based on a particular condition before sending it to the integration platform. There is no default value for this property. Note: This property is not applicable when the source connection is a query statement or file. This property enables data filtering when you select a table. |
CommitFrequency | T | 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. |
ConstraintDDL | T | Allows you to specify some additional SQL data definition language statements to be executed after their target table is created. This is similar to the support provided for SQL Pass-thru in the SQL import connectors. Each line must be a valid DDL statement. For example, you could have the statements CREATE UNIQUE INDEX index1 ON mytable (Field1 ASC)CREATE INDEX index2 ON mytable (Field2, Field3) These statements would create two indices on the table mytable. The first one 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 executed only if the replace mode is used for the target. If there are any errors, the errors are written to the error and event log file. During the transformation, the transformation error dialog box appears. If you want to ignore the DDL errors, you can continue the transformation. ConstraintDDL also supports an escaping mechanism that allows users to specify DDL in the native SQL of the DBMS. Any statement that is preceded by an @ is sent straight to the DBMS. The statement @CREATE INDEX pk_mytable ON mytable (Field1, Field2) WITH PRIMARY is a DDL statement for creating a primary key for the table mytable. Note: This option works only in REPLACE mode. |
UseCursors | T | The UseCursors property allows you to turn cursor support on and off. The default is false. If you set the property to true and the specified driver does not support cursor inserts, the SQL INSERT mode of adding records is used. For exports, cursor support is supposed to enhance the performance of inserting records. For database servers, there is no noticeable change in insert speed. They seem to execute prepared queries about as quickly as they handle cursor inserts. |
DriverOptions | ST | Enter Informix client connection information, such as database, server, and protocol, in the format shown in this example: Database=sysutils;Server=ol_qadb1;Protocol=onsoctcp |
DriverCompletion | ST | 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 is the default option. This option prompts the user for any information that 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. |
MaxDataLength | ST | The maximum data length for long data types. Default is 1 MB, 1048576. You can reset this number as you choose based on your available memory capabilities and Target requirements. Some drivers have limitations concerning the maximum data length they can handle. If you choose a Source or target connector and the default setting is not 1 MB, then Map Designer has preset the default in respect for the capabilities of that particular driver. It is not recommended that the MaxDataLength property be set any higher under those conditions. |
PrimaryKey | ST | The PrimaryKey property allows you to specify a list of field names that are used to make the primary key. The field names are delimited by commas. If the PrimaryKey property contains one or more field names, these names are included in the SQL CREATE statement when the connector is in replace mode. There is one additional requirement for using the PrimaryKey property. The driver must support integrity enhancement facility (IEF). Only the more advanced drivers support this. |
Synonyms | ST | 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 | ST | The SystemTables property is applicable only if the user is 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 | ST | The Translation Isolation option allows you to specify any one of five different isolation levels when reading from or writing to a database table. The default for version 3.x, 3.5 and IBM DB2 Universal Database 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 five 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 any of P1, P2, and P3. • VERSIONING – Provides SERIALIZABLE transactions, but does so without a significant impact on concurrency. |
Views | ST | 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. |
CodePage | ST | The code page translation table tells Map Designer which encoding to use for reading and writing data. The default is ANSI, which is the standard in the US. The following code pages are available: • ANSI • OEM • 0037 US (EBCDIC) • 0273 Germany (EBCDIC) • 0277 Norway (EBCDIC) • 0278 Sweden (EBCDIC) • 0280 Italy (EBCDIC) • 0284 Spain (EBCDIC) • 0285 UK (EBCDIC) • 0297 France (EBCDIC) • 0437 MSDOS United States • 0500 Belgium (EBCDIC) • 0850 MSDOS Multilingual (Latin 1) • 0860 MSDOS Portuguese • 0861 MSDOS Icelandic • 0863 MSDOS Canadian French • 0865 MSDOS Nordic • 1051 Roman-8 |