Skip to main content

MongoDB Source Connector

The MongoDB source connector in DataSync lets you retrieve data from MongoDB instances for loading or synchronizing in your data warehouse. After creating all required source connections, configure your destination source to complete the connection setup.

important

The Consolidation extraction is currently not available for MongoDB source connections.

Create a source connection in DataSync

  1. Log in to DataSync.
  2. From the welcome screen, select Connections.
  3. Next to Source Connections, click New.
  4. Select MongoDB.
  5. In the Connection Properties panel, enter the connection properties.
  6. (Optional) In the Additional Connection Properties panel, select Add property and enter the parameters for each property.
  7. In the Advanced Settings panel, configure the settings, including the Tracking Type and other values according to your requirements.
  8. Click Save.

important

For properties that contain arrays, the inferred precision may be underestimated. This can cause truncation errors at extraction. Recommendation: Set the precision to MAX for these columns in your destination table to avoid failures.

Parameters

Connection properties

ParameterDescription
DescriptionUnique name for the connection. Example: MongoDB.
ServerHostname or IP address of the MongoDB server.
Example: mongodb.example.com
PortPort number of the server. Default: 27017.
DatabaseName of the MongoDB database to connect to. Example: SalesData.
Authentication ModeAuthentication method for the database:
  • Basic – Challenge‑response authentication with username and password stored in the MongoDB database.
  • NoAuth – No authentication.
UsernameAccount username stored in the MongoDB database Example: mongoUser.
PasswordPassword associated with the username.
Authentication DatabaseName of the database used for authentication if different from the database specified in Database.
Example: admin
Flatten ObjectsOption to convert nested object properties into separate columns. If disabled, objects are returned as JSON strings.
Use SSL/TLSEncryption setting for securing the connection with SSL/TLS. Requires an SSL certificate.
Allows Invalid Server CertificatesOption to accept all certificates from the server when using SSL/TLS. Not recommended due to security risks.
Row Scan DepthNumber of rows scanned in the collection to infer schema. A higher value produces a more accurate schema but may reduce performance. Default: 1000.
Verbosity
  • 1 – Log queries, row counts, execution start/end, errors.
  • 2 – Includes level 1 plus cache queries, HTTP headers.
  • 3 – Includes level 2 plus request/response bodies.
  • 4 – Includes level 3 plus transport-level communication.
  • 5 – Includes level 4 plus all interface commands.
Enable PoolingConnection pooling option for performance.
Pool idle timeoutMaximum idle time for connections before returning them to the pool, in seconds.
Max Pool SizeMaximum number of connections allowed in the pool.
Pool wait timeMaximum wait time for connection allocation before error is thrown, in seconds.

Flatten Objects example

Consider the following sales document:

{
"orderId": 10592,
"customer": { "id": 456, "name": "Acme Corp" },
"shipping": { "city": "New York", "state": "NY" }
}
  • If Flatten Objects is enabled, the document appears as:

    Column NameData TypeExample Value
    orderIdInteger10592
    customer.idInteger456
    customer.nameStringAcme Corp
    shipping.cityStringNew York
    shipping.stateStringNY
  • If Flatten Objects is disabled, nested properties remain inside JSON:

    {"city": "New York", "state": "NY"}

Additional connection properties

Additional connection string properties not specified in the Connection Properties panel. For each property added, you can choose Visible or Encrypted. Selecting Encrypted hides the value from the interface and stores it encrypted in the back end, such as when defining passwords.

ParameterDescription
PropertyConnection string property that defines the action or behavior. Example: ReadOnly
ValueValue for the property. Example: True
TypeVisibility of the property: Visible or Encrypted.

Advanced settings

Advanced settings control how the MongoDB connector tracks changes, handles regional and time configuration, and processes data batches during extraction. These options allow fine‑tuning for performance and accuracy, and should be configured according to your system environment and operational requirements.

SettingDescription
Tracking TypeMethod for tracking changes: None or Date.
RegionRegion setting for the connector, if required by your setup.
Time ZoneTime zone matching the MongoDB application server.
Time OffsetRefresh offset in seconds to compensate for timing issues in record selection. Minimum value is 0; maximum is 3600 seconds.
Batch SizeQuantity of records processed in each batch during extraction. Larger batch sizes increase memory usage but can improve performance up to a point. The default value is 2000 and the maximum should not exceed 10000 records. Adjust according to your network speed and disk performance; in most cases the default (2000) works best.

Example