To best support your SQL server and the needs of a migration, it's recommended that all production Migration Manager for Email Archives deployments run on a dedicated instance of Microsoft SQL Server.
Migration Manager for Email Archives is a feature-rich product and can therefore result in very diverse SQL Server load profiles between customer deployments. As Migration Manager for Email Archives scales, additional databases and the associated increase in load will require scaling of the SQL Servers to meet the load.
Although Enterprise Edition of Microsoft SQL Server is recommended, Standard Edition may be used if the SQL instance uses the recommended (not minimum) resources associated with the size of migration you are performing. Planning for additional time will be required to accommodate regularly required offline maintenance.
There are many factors which may influence the deployment, but an initial server sizing guideline would be to provision the CPU cores and RAM described in the information below arranged in as many servers as desired, evenly distributing the Migration Manager for Email Archives databases if deployed as multiple SQL servers.
The SQL Server that manages these databases must reside on a separate server than the Migration Manager for Email Archives core and modules. The only exception is for a non-production pilot/demonstration system.
Migration Manager for Email Archives keeps track of every item it exports/imports for auditing purposes. It places a reliance on SQL Server for this task. An adequately prepared SQL Server that meets the recommended specification is essential for a fast migration. Ensuring that an adequately prepared SQL Server which meets the recommended specification is essential for a fast migration.
NOTE: Performance of the migration will be impacted if the SQL Server environment is not sufficient for the needs of the migration.