{"id":2680,"date":"2021-02-23T08:00:00","date_gmt":"2021-02-23T05:00:00","guid":{"rendered":"https:\/\/www.dataplatform.gr\/?p=2680"},"modified":"2024-12-03T21:05:55","modified_gmt":"2024-12-03T18:05:55","slug":"pos-kanoyme-online-migration-ena-instance-apo-on-premise-se-azure-managed-instance-sto-cloud-a","status":"publish","type":"post","link":"https:\/\/www.dataplatform.gr\/en\/pos-kanoyme-online-migration-ena-instance-apo-on-premise-se-azure-managed-instance-sto-cloud-a\/","title":{"rendered":"How to online migrate an instance from on-premise to Azure Managed Instance in the Cloud (Azure Database Migration Service)"},"content":{"rendered":"

In this article we will analyze the way we can do it online migration<\/strong> of a SQL Server Instance from<\/strong> on-premise in Azure Managed Instance<\/strong>. To be able to do it online, with near zero downtime we will use it Azure Database Migration Service<\/strong> in hybrid mode<\/strong>. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The process is done using an installed client worker service in Windows Server 2012 and later versions in collaboration with the Database Migration Service in Azure. <\/p>\n\n\n\n

The example<\/h2>\n\n\n\n

It is a complex process so we should follow the steps very strictly.<\/p>\n\n\n\n

First the process requires that we have created the Azure SQL Managed Instance. We can see how this is done in detail in this article<\/a>.<\/p>\n\n\n\n

To start setting up the migration process, we will search for it Azure Database Migration Services<\/em>.<\/p>\n\n\n\n

\"\"
1<\/figcaption><\/figure>\n\n\n\n

We choose Add<\/em>.<\/p>\n\n\n\n

\"\"
2<\/figcaption><\/figure>\n\n\n\n

We put Resource Group<\/em> which is the Managed Instance we will migrate, a name in the service and we choose Hybrid <\/strong>Service mode<\/em>.<\/p>\n\n\n\n

\"\"
3<\/figcaption><\/figure>\n\n\n\n

At this point we should make one Azure App<\/strong> which will be responsible for communicating with each other client worker<\/em> and his Database Migration Service<\/em>.<\/p>\n\n\n\n

So let's go to Tenant<\/em> of Azure Active Directory<\/em> that we have, App registrations<\/em> and New registration<\/em>.<\/p>\n\n\n\n

\"\"
4<\/figcaption><\/figure>\n\n\n\n

We set a name and leave the rest as it is.<\/p>\n\n\n\n

\"\"
5<\/figcaption><\/figure>\n\n\n\n

Now we should turn to Azure Database Migration Service<\/em> that we built in the beginning and give the Contributor role to have the access you require. So we choose Access Control<\/em>, Add role assignment<\/em>, we define the role and look for the name of the application we defined.<\/p>\n\n\n\n

\"\"
6<\/figcaption><\/figure>\n\n\n\n

We should do the same procedure for the application below Subscription<\/strong> that we have. <\/p>\n\n\n\n

\"\"
7<\/figcaption><\/figure>\n\n\n\n

We go back to the Azure Database Migration Service and select the tab Hybrid<\/em> and Installer download<\/em>. From there we will download the client worker that we will install.<\/p>\n\n\n\n

\"\"
8<\/figcaption><\/figure>\n\n\n\n

After it is downloaded and we unzip it, we should put the parameters it asks for in the dmsSettings.json<\/strong>.<\/p>\n\n\n\n