Azure Data Studio - Azure SQL Migration extension thinks the Managed Instance is still in 'Creating' state.

Vlasopoulos V 5 Reputation points
2023-02-28T11:28:45.1133333+00:00

In step 3 of the Azure SQL Migration where the user chooses the managed instance:

Error:

The managed instance 'managedinstance' is unavailable for migration because it is currently in the 'Creating' state. To continue, select an available managed instance.

User's image

But this managed instance's state has been "ready" for about 4-5 hours.

User's image

Do I need to wait even more time for the Azure SQL Migration extension of Azure Data Studio to see that the state is not 'Creating' anymore? Is there any action needed from me?

Azure Database Migration service
Azure SQL Database
SQL Server Migration Assistant
SQL Server Migration Assistant
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
492 questions
Azure Data Studio
Azure Data Studio
A cross-platform database tool for data professionals using on-premises and cloud data platforms on Windows, macOS, and Linux.
97 questions
{count} votes

2 answers

Sort by: Most helpful
  1. ShaktiSingh-MSFT 13,271 Reputation points Microsoft Employee
    2023-03-30T06:06:17.07+00:00

    Hi Rune Moberg,

    Welcome to Microsoft Q&A forum and thanks for using Azure Services.

    As I understand, you are getting same error as Azure SQL Managed Instance unavailable in Azure Data Studio.

    Make sure you have installed the official release of the Azure SQL Managed Instance extension. Follow the steps in the Azure Data Studio documentation. In the Extensions pane, search for "Managed Instance", and install it there. After it's installed, you'll get notified automatically about any future extension updates.

    With the extension installed, you'll see a Managed Instance tab in Azure Data Studio. Here you can find information specific for your managed instance.

    Reference: https://learn.microsoft.com/en-us/sql/azure-data-studio/extensions/azure-sql-managed-instance-extension?view=sql-server-ver16

    Hope this helps. If not:

    Could you please tell what type of migration you are performing?

    At what step error comes up? Screenshot would help.

    Thank you.

    1 person found this answer helpful.

  2. ShaktiSingh-MSFT 13,271 Reputation points Microsoft Employee
    2023-02-28T11:59:22.3633333+00:00

    Hi @Vlasopoulos V ,

    Welcome to Microsoft Q&A forum and thanks for using Azure services.

    Regarding the issue which you have in Azure Data Studio - Azure SQL Migration extension thinks the Managed Instance is still in 'Creating' state.

    Could you please try to close and re-open Azure Data Studio and give it a try if this helps.

    If not, please let us know if you performing Online or Offline migration?

    Also, I would request you to go through the Known Issues in Azure SQL Managed Instance limitations:

    Migrating to Azure SQL Managed Instance by using the Azure SQL extension for Azure Data Studio has the following limitations:

    • If migrating a single database, the database backups must be placed in a flat-file structure inside a database folder (including the container root folder), and the folders can't be nested, as it's not supported.
    • If migrating multiple databases using the same Azure Blob Storage container, you must place backup files for different databases in separate folders inside the container.
    • Overwriting existing databases using DMS in your target Azure SQL Managed Instance isn't supported.
    • Configuring high availability and disaster recovery on your target to match source topology isn't supported by DMS.
    • The following server objects aren't supported:
      • SQL Server Agent jobs
      • Credentials
      • SSIS packages
      • Server audit
    • You can't use an existing self-hosted integration runtime created from Azure Data Factory for database migrations with DMS. Initially, the self-hosted integration runtime should be created using the Azure SQL migration extension in Azure Data Studio and can be reused for further database migrations.
    • A single LRS job (created by DMS) can run for a maximum of 30 days. When this period expires, the job is automatically canceled thus your target database gets automatically deleted.

    Please ensure these are checked.

    Hope this should help. If not, please share inputs so that we may further assist.