Separator character for arrays and nested documents. The nested column separator must be consistent across connections used in a mapping. For example, if one connection uses the period (.) as the nested column separator and another connection in the same mapping uses the underscore (_) as the separator, then the mapping fails.

The maximum number of array elements that the ODBC driver flattens into multiple nested columns.

Server that you prefer to read data from if you configure replica sets. You can select one of the following server options:

Primary. The
Data Integration Service
reads data from the primary server. If the primary server is offline, the session fails.
Primary Preferred. The
Data Integration Service
reads data from the primary server if the primary server is available. If the primary server is offline, the
Data Integration Service
reads data from the secondary server.
Secondary. The
Data Integration Service
reads data from the secondary server. If the secondary server is offline, the session fails.
Secondary Preferred. The
Data Integration Service
reads data from the secondary server if the secondary server is available. If the secondary server is offline, the
Data Integration Service
reads data from the primary server.
Nearest. The
Data Integration Service
reads data from the nearest available server.

Number of rows to scan in the schema definition. You can select one of the following sampling strategies:

Start. Scans the specified number of rows from the start.
End. Scans the specified number of rows from the end.
Random. Scans the specified number of rows in random order.

The string column length to use for the fields. You can select one of the following string column lengths:

Standard. The string column length to use for the standard fields. Default is 255.
Container. The string column length to use for the container fields. Default is 511.
DocumentAsJSON. The string column length to use for the documentAsJSON fields. Default is 1023.

The

Data Integration Service

maps the String datatype to SQL_WVARCHAR ODBC instead of SQL_VARCHAR.

Read or write data as a JSON document. If enabled, the driver reports a special column named documentAsJSON that retrieves or stores whole documents as JSON formatted strings.

Show the container columns when the Integration Service generates the metadata.

Not Applicable.

Calls the MongoDB CheckGetLastError() function to check for failures after a write operation.

The Informatica MongoDB ODBC driver updates multiple rows for each

Data Integration Service

write call.

The

Data Integration Service

does not write columns with NULL value to a MongoDB target.

Truncate the document size to 16 MB when you load data to MongoDB.

Read metadata changes from the MongoDB database or from a local file. Required if you choose to store the metadata in a local file.