Run Pre-Migration Analysis
On this page
You can run Pre-Migration Analysis against a relational database to review potential migration risks before migrating data to MongoDB. Running Pre-Migration Analysis generates a report that identifies risks and provides guidance on how to mitigate them.
About this Task
Relational Migrator typically takes 5-10 minutes to crawl the database, though it can take longer if the machine running Relational Migrator isn't near the database server.
Important
Relational Migrator supports Pre-Migration Analysis for Microsoft SQL Server, MySQL, Oracle, and PostgreSQL. Pre-Migration Analysis isn't supported for databases connected through a JDBC driver. For more information on supported databases and versions, see Supported Databases and Versions.
Before you Begin
To run Pre-Migration Analysis, you need a project with a live database connection.
Steps
Click Run analysis
If you didn't save credentials when saving the relational database connection, enter them now and then click Connect and run analysis to continue.
Relational Migrator analyzes the connected source database. You can click Terminate if you need to stop the process. Once complete, Relational Migrator shows the resulting report.
Important
If Relational Migrator encounters errors, it displays the message "An error occurred during the analysis. As a result, there may be information missing from the report." If this happens, click Rerun analysis on the report Summary page to run analysis again. If the problem persists, please contact your account representative.
Next Steps
After running Pre-Migration Analysis, review the report and follow the recommended actions. You can then re-run analysis by navigating to the report Summary and clicking Rerun analysis to see if any risks remain.