Use SQL Server Management Studio to Determine SQL Database compatibility before migration to Azure SQL Database
In this article you learn to determine if a SQL Server database is compatible to migrate to SQL Database using the Export Data Tier Application Wizard in SQL Server Management Studio.
Using SQL Server Management Studio
Verify that you have the latest version of SQL Server Management Studio. New versions of Management Studio are updated monthly to remain in sync with updates to the Azure portal.
It is recommended that you always use the latest version of Management Studio to remain synchronized with updates to Microsoft Azure and SQL Database. Update SQL Server Management Studio.
- Open Management Studio and connect to your source database in Object Explorer.
Right-click the source database in the Object Explorer, point to Tasks, and click Export Data-Tier Application…
In the export wizard, click Next, and then on the Settings tab, configure the export to save the BACPAC file to either a local disk location or to an Azure blob. A BACPAC file is saved if you have no database compatibility issues. If there are compatibility issues, they are be displayed on the console.
To skip exporting data, click the Advanced tab and clear the Select All checkbox. Our goal at this point is only to test for compatibility.
Click Next and then click Finish. Database compatibility issues, if any, appear after the wizard validates the schema.
- If no errors appear, your database is compatible and you are ready to migrate. If you have errors, you need to fix them. To see the errors, click Error for Validating schema.
- If the *.BACPAC file is successfully generated, then your database is compatible with SQL Database, and you are ready to migrate.
- Newest version of SSDT
- Newest version of SQL Server Management Studio
- Fix database migration compatibility issues
- Migrate a compatible SQL Server database to SQL Database