My migration extension is not working in my Data Studio.

Hi Nischay •,

Welcome to Microsoft Q&A forum.

As I understand, you are trying to do migration from aws rds to azure sql managed instance. You have connected database in data studio and installed the migration extension but it's not showing up in the databases manage section.

Could you please ensure that all prerequisites meet:

1). Have an Azure account that's assigned to one of the following built-in roles:

• Contributor for the target instance of Azure SQL Managed Instance and for the storage account where you upload your database backup files from a Server Message Block (SMB) network share
• Reader role for the Azure resource groups that contain the target instance of Azure SQL Managed Instance or your Azure Storage account.
• Owner or Contributor role for the Azure subscription (required if you create a new Database Migration Service instance)

As an alternative to using one of these built-in roles, you can assign a custom role.

2). Ensure that the logins that you use to connect the source SQL Server instance are members of the SYSADMIN server role or have CONTROL SERVER permission.

3). If you're migrating a database that's protected by Transparent Data Encryption (TDE), the certificate from the source SQL Server instance must be migrated to your target managed instance before you restore the database. For more information about migrating TDE-enabled databases, see Tutorial: Migrate TDE-enabled databases (preview) to Azure SQL in Azure Data Studio.

If your database contains sensitive data that's protected by Always Encrypted, the migration process automatically migrates your Always Encrypted keys to your target managed instance.

4). If your database backups are on a network file share, provide a computer on which you can install a self-hosted integration runtime to access and migrate database backups. The migration wizard gives you the download link and authentication keys to download and install your self-hosted integration runtime.

In preparation for the migration, ensure that the computer on which you install the self-hosted integration runtime has the following outbound firewall rules and domain names enabled:

• If you use a self-hosted integration runtime, make sure that the computer on which the runtime is installed can connect to the source SQL Server instance and the network file share where backup files are located.
• Enable outbound port 445 to allow access to the network file share. For more information, see recommendations for using a self-hosted integration runtime.
• If you're using Database Migration Service for the first time, make sure that the Microsoft.DataMigration resource provider is registered in your subscription. You can complete the steps to register the resource provider.

----------------------------------Important:--------------------------------

For the list of Azure regions that support database migrations by using the Azure SQL Migration extension for Azure Data Studio (powered by Azure Database Migration Service), see Azure products available by region.

Known issues and limitations:

Database Migration Service doesn't support overwriting existing databases in your target instance of Azure SQL Managed Instance, Azure SQL Database, or SQL Server on Azure Virtual Machines.

Database Migration Service doesn't support configuring high availability and disaster recovery on your target to match the source topology.

The following server objects aren't supported:

• SQL Server Agent jobs
• Credentials
• SQL Server Integration Services packages
• Server audit

For a complete list of metadata and server objects that you need to move, refer to the detailed information available in Manage Metadata When Making a Database Available on Another Server.

SQL Server 2008 and earlier as target versions aren't supported for migrations to SQL Server on Azure Virtual Machines.

If you use SQL Server 2014 or SQL Server 2012, you must store your source database backup files in an Azure storage blob container instead of by using the network share option. Store the backup files as page blobs. Block blobs are supported only in SQL Server 2016 and later versions.

You can't use an existing self-hosted integration runtime that was created in Azure Data Factory for database migrations with Database Migration Service. Initially, create the self-hosted integration runtime by using the Azure SQL Migration extension for Azure Data Studio. You can reuse that self-hosted integration runtime in future database migrations.

Azure Data Studio currently supports both Microsoft Entra ID/Windows authentication and SQL logins for connecting to the source SQL Server instance. For the Azure SQL targets, only SQL logins are supported.

Please check above pointers and let us know if all works fine.

If fine, then please share configuration details of the target so that we can further inspect.

Thanks