Table of Content
What is SQL Server Migration Assistant?
Microsoft SQL Server Migration Assistant (SSMA) is a commonly used tool to migrate databases from other database systems like Oracle, MySQL, PostgreSQL to SQL Server or Azure SQL automatically.
When you utilize SSMA to convert a database, it will automate much of the process involved in:
- Assessing the source database – analyzing the database to identify potential compatibility issues and generating a report.
- Converting database schema and objects – converting tables, views, stored procedures, functions, triggers, etc. to SQL Server or Azure format.
- Migrating the database – transferring schema and data to the target system.
- Testing and validating – comparing source and target databases to ensure migration success.
What are the benefits of using SSMA?
These are the key features of using SSMA to migrate databases to SQL Server or Azure:
- Assessment Report: Analyzes the source database and provides reports about potential migration issues, estimated effort, and compatibility levels.
- Support multiple databases: Supports migrating from many different database types including Oracle, IBM DB2, MySQL, and Microsoft Access.
- Automated Conversion: Converts source database schemas (tables, indexes, constraints, views, etc.) to equivalent SQL Server or Azure SQL structures. It also attempts to translate procedural code (PL/SQL, T-SQL, etc.) automatically.
- Integration with Azure: Supports migrations to Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure Virtual Machines.
What SSMA Supported Database Systems?
SQL Server Migration Assistant has different versions for different databases; each one is a separate installer. For example, SSMA for Oracle differs from SSMA for MySQL.
| SSMA Version | Source Database | Target System |
|---|---|---|
| SSMA for Oracle | Oracle Database (versions 9i – 19c) | SQL Server (2012 – 2022), Azure SQL Database, Azure SQL Managed Instance |
| SSMA for MySQL | MySQL (versions 4.1 – 8.0) | SQL Server, Azure SQL Database, Azure SQL Managed Instance |
| SSMA for DB2 | IBM Db2 for LUW (versions 9.7 – 11.5) | SQL Server, Azure SQL Database, Azure SQL Managed Instance |
| SSMA for Sybase | SAP Adaptive Server Enterprise (ASE) (versions 12.5 – 16.x) | SQL Server, Azure SQL Database, Azure SQL Managed Instance |
| SSMA for Access | Microsoft Access (versions 2000 – 2019, and Microsoft 365) | SQL Server, Azure SQL Database, Azure SQL Managed Instance |
Full Guide: How to use SQL Server Migration Assistant
Before migrating a database to SQL Server or Azure, check the SQL Server Migration Assistant requirements:
| Component | Requirement |
|---|---|
| Operating System | Windows 10 or later, or Windows Server 2016 / 2019 / 2022 |
| Processor | x64 processor, 1.8 GHz or faster (multi-core recommended) |
| Memory (RAM) | Minimum 4 GB (8 GB or more recommended for large databases) |
| Disk Space | At least 100 MB for SSMA installation (plus space for data migration files and logs) |
Part 1. How to install SQL Server Migration Assistant
Whether you need SSMA for Oracle, MySQL, IBM DB2, SAP ASE, or Microsoft Access, follow these steps:
Step 1. Go to the Official Microsoft Download Center and find the correct SSMA version.
Step 2. Click the specific download page, press “Download”, choose the correct installer (.msi file), and confirm.
Step 3. After downloading, right-click the installer and choose “Run as Administrator.”
Step 4. Follow the on-screen prompts: Accept license terms → Choose installation folder → Click “Install.”
Step 5. Once complete, click “Finish.”
Step 6. Download and install .NET Framework (from Microsoft’s official page).
Step 7. On Windows Server, open Server Manager Dashboard → Add Roles and Features to complete installation.
Part 2. Step-by-step process to use SQL Server Migration Assistant
Step 1. Open SQL Server Migration Assistant from the Start Menu.
Step 2. Click File > “New Project“. Enter project name, location, source type, and target, then click “OK“.
Step 3. Click “Connect to Source” and provide connection details (server name, user ID, password, and database name).
Step 4. SSMA lists all available schemas and objects.
Step 5. Click “Connect to SQL Server” (or Azure SQL Database), provide SQL Server name, authentication type, and database name, then connect.
Step 6. Click “Assess” to generate a Migration Assessment Report.
Step 7. Select schemas or objects to migrate and click “Convert Schema“.
Step 8. Review the converted schema in the Metadata Explorer pane and modify scripts if needed.
Step 9. Click “Synchronize with Database” (or “Deploy Schema”) to create target objects.
Step 10. Select tables, right-click, and choose “Migrate Data“. Wait for the migration to finish.
Note: You can automate migrations using SSMA’s command-line interface (CLI):
SSMAConsole.exe /s "C:\Projects\MyMigration.ssmaproject" /vBest Recommended Way to Migrate Database to SQL Server or Azure
Sometimes, you may encounter issues using SSMA, especially in more complex or mission-critical environments that require near-zero downtime. In such cases, consider a professional migration solution like i2Migration.
i2Migration, developed by Information2, is a unified enterprise migration platform that supports full-system, database, file/NAS, cloud, and hybrid migration scenarios. It provides broad heterogeneous support, including Oracle, SQL Server, MySQL, PostgreSQL, DB2, and Informix, and supports real-time replication — ensuring non-disruptive, continuous migration.
Conclusion
In this post, we introduced SQL Server Migration Assistant, its supported systems, requirements, and step-by-step usage guide. If your project focuses purely on moving a supported source to SQL Server or Azure SQL, SSMA is an excellent choice.
However, for more complex, heterogeneous environments or live mission-critical systems requiring negligible downtime or hybrid migrations, i2Migration provides a more robust enterprise-grade alternative.