Hi We used the data migration extension in Azure data studio to migrate sql server db to SQL MI We stored all the backups to hte azure blob container We started the migration Once all the backups showed restored. We marked the db as read only. We selected complete cutover. The migration status show succeeded When dont see not any objects on the SQL MI for table / stored procedure /Functions .This was done after we fixed the errors we encoutnered on migration For another database we are able to view objects however the row count and checksum dont match

Hello Nitya V , Thanks for reaching out in the Microsoft Q&A! To troubleshoot the issue of missing objects in SQL Managed Instance (SQL MI) after migrating a SQL Server database using the Azure SQL Migration extension, verify that you selected the correct target database during the cutover process and that Azure SQL MI firewall settings allow necessary connections. Check the Azure SQL Migration Service logs for any errors, and ensure you're using elevated permissions to access the target database, as objects might be hidden or inaccessible due to permissions. Confirm if you used online or offline migration and that it aligns with your expectations. For further assistance, review the Azure SQL Migration documentation . If you find this helpful, please accept this answer to close the thread. Thanks!

Azure Data Studio - Data Migration Extension

Nitya V 40

We used the data migration extension in Azure data studio to migrate sql server db to SQL MI

We stored all the backups to hte azure blob container

We started the migration
Once all the backups showed restored.
We marked the db as read only.
We selected complete cutover.
The migration status show succeeded

When dont see not any objects on the SQL MI for table / stored procedure /Functions .This was done after we fixed the errors we encoutnered on migration

For another database we are able to view objects however the row count and checksum dont match

GeethaThatipatri-MSFT 28,617 Reputation points Microsoft Employee

2024-05-29T15:23:49.09+00:00
@Nitya V The description is a bit confusing so a few clarification questions1. "migrate sql server db to SQL MI": Do you mean a database from On-premises sql instance to MI? or from Azure SQL Database to Azure SQL Managed Instance? I want to guess this is the first option since you refer to backups but need confirmation.

Did you validate that the right source folders were selected? Were the backup files in the source folder confirmed to be from the right databases? Regards Geetha
Nitya V 40 Reputation points

2024-05-30T07:54:41.0233333+00:00

I meant a database source on On-premises sql to target is azure sql managed instance

1 answer

Gowtham CP 3,655 Reputation points

2024-05-24T18:49:45.2066667+00:00

Hello Nitya V ,

Thanks for reaching out in the Microsoft Q&A!

To troubleshoot the issue of missing objects in SQL Managed Instance (SQL MI) after migrating a SQL Server database using the Azure SQL Migration extension, verify that you selected the correct target database during the cutover process and that Azure SQL MI firewall settings allow necessary connections. Check the Azure SQL Migration Service logs for any errors, and ensure you're using elevated permissions to access the target database, as objects might be hidden or inaccessible due to permissions. Confirm if you used online or offline migration and that it aligns with your expectations. For further assistance, review the Azure SQL Migration documentation. If you find this helpful, please accept this answer to close the thread. Thanks!
Please sign in to rate this answer.
Gowtham CP 3,655 Reputation points

2024-05-27T04:48:50.0666667+00:00

Hello Nitya V ,

We haven't heard back from you. Could you please provide an update on your issue? If you have any questions or concerns, feel free to reach out to us. If the information provided has been helpful, please consider marking it as the accepted answer to close this case. Doing so will assist others with similar questions in finding solutions more easily.

Nitya V 40 Reputation points

2024-05-27T06:35:07.8233333+00:00

Thanks .If it were a firewall.The other database that was migrated should have behaved the same.

eg

testMarket migrated sqlmi-testMarket - where table are not visible/object are not found

testFinance migrated sqlmi-testFinance - where table are visible/object are found however rowcount and checksum donot match

My concern is are we missing any step during online migration and its is reliable in comparison to traditional migrations

Gowtham CP 3,655 Reputation points

2024-05-27T08:36:28.95+00:00

You're right, Nitya. If the firewall were the issue, both testMarket and testFinance would have similar problems. Since testFinance objects are visible, the firewall is less likely the cause. For missing objects in testMarket, check for schema changes during migration and ensure schema objects are created in the target database. Use SQL queries like sys.schemas, sys.tables, and sys.objects to identify any hidden schema objects. For data discrepancies in testFinance, consider potential data corruption during migration or changes made to the source database after the migration snapshot. Use a validation script to compare source and target data. When choosing between online and traditional migration, consider factors like acceptable downtime and risk of inconsistencies. Refer to the Azure SQL Database Migration Guide and Troubleshooting Azure SQL Database Migration for more information. By investigating these issues, you should resolve the problems in both databases.

Nitya V 40 Reputation points

2024-06-03T10:59:34.4966667+00:00

Does it support differential backup as it seems to always skip differential backup placed in the blob
Sign in to comment

Share via

Azure Data Studio - Data Migration Extension

1 answer