Migration jobs transfer data from your relational database to MongoDB. Migration jobs use project-level Data Modeling to distribute data to your MongoDB database.
Types of Migration Jobs
Relational Migrator offers snapshot migration jobs that run once for a point-in-time migration strategy.
Compatibility
Some databases might have specific requirements, and Relational Migrator generates a script to modify source databases as necessary. See the following pages to learn more about configuration prerequisites for each type of relational database:
Behavior
Migration jobs are non-idempotent by default. Relational Migrator inserts new documents and embeded arrays each time a job is run, with the option to delete each existing collection at the start of the sync dialogue. You can enable idempotency to delete inserts from the previous migration job automatically.
To enable idempotent inserts for documents and embedded arrays, set
migrator.engine.transform.idempotency: true in the
user.properties file. Enabling idempotency may have substantial
performance impact on large jobs.
Indexes
Relational Migrator creates new indexes in your MongoDB collections to supplement the migration process. For best performance, review the indexes in your collection after migration to ensure that they best fit your application usage patterns.
Relational Migrator does not create new indexes in the relational database. Relational Migrator has read-only access to your source database.
See the following pages for more information on revewing your collection indexes:
Get Started
You can perform the following tasks from the Data Migration tab.
Task | Description |
|---|---|
Create a migration job which uses the defined mapping rules and migration options. | |
View metadata, execution status, and issues for a migration job. | |
Cancels the execution of a migration job. |