{"id":2744,"date":"2023-02-27T07:00:00","date_gmt":"2023-02-27T04:00:00","guid":{"rendered":"https:\/\/www.dataplatform.gr\/?p=2744"},"modified":"2023-12-04T00:10:31","modified_gmt":"2023-12-03T21:10:31","slug":"pos-kanoume-migrate-vasi-me-dma","status":"publish","type":"post","link":"https:\/\/www.dataplatform.gr\/en\/pos-kanoume-migrate-vasi-me-dma\/","title":{"rendered":"How to migrate a SQL Server database to Azure using Data Migration Assistant"},"content":{"rendered":"

Many times we will need to migrate databases to a newer version or move them to Azure. In such a transfer there is a possibility that some components are not compatible and need corrections before we start the migration.<\/p>\n\n\n\n

The tool that provides us with help to find problems that may affect the migration and offers instructions on how to solve them is Data Migration Assistant<\/strong>. It also has the ability to undertake to carry out the offline migration<\/strong>.<\/p>\n\n\n\n

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

Can we let's download <\/strong>the Data Migration Assistant from here<\/a>.<\/p>\n\n\n\n

In case we migrate to Azure <\/strong>we should be able to access the Azure infrastructure with either one Public Endpoint<\/strong> (Internet), either with ExpressRoute <\/strong>or else with VPN<\/strong>.<\/p>\n\n\n\n

*If the size and number of bases is large, its use is recommended Azure Database Migration Service<\/strong> which can also perform online migrations. Detailed information and a migration example are available at this article<\/a>.<\/em><\/p>\n\n\n\n

In the rest of the article we will see how to transfer a database from on-premise SQL Server <\/strong>in Azure SQL Database<\/strong>.<\/p>\n\n\n\n

An Azure SQL Database should first be created as described in this article<\/a>.<\/p>\n\n\n\n

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

We open it Data Migration Assistant <\/strong>and we choose Migration<\/strong>.<\/p>\n\n\n\n

We define a project name, that we want to transfer from Source SQL Server<\/em> in Target Azure SQL Database<\/em> and that we want to transfer it too base shape and data<\/em>.<\/p>\n\n\n\n

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

We define him SQL Server<\/em> which is currently hosting the base. In our case it is the server itself, that's why I put it localhost<\/em>. Since it is the server itself, it was convenient to use as Authentication type<\/em> Windows<\/em> so that he doesn't ask me credentials<\/em>.<\/p>\n\n\n\n

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

In the next step we put its name in Server name Endpoint <\/strong>(private or public) in my case I had made it public during the creation of the database, so there is access via Internet<\/strong>.<\/p>\n\n\n\n

For credentials <\/strong>we can use his server admin <\/strong>which asks Mrwhen creating the Azure SQL Database Server<\/em>.<\/p>\n\n\n\n

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

We select the database we want and it will show us all the objects it contains. In our case I had made only one table.<\/p>\n\n\n\n

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

In the next step we will create the TSQL <\/strong>scripts that need to be done deploy <\/strong>in Azure SQL Database<\/em> to make the same shape.<\/p>\n\n\n\n

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

Then we will select the tables that we will transfer their data.<\/p>\n\n\n\n

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

With what we choose migrate <\/strong>will start the process and inform us about the status of the work.<\/p>\n\n\n\n

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

Once the message appears Migration successful<\/strong>. If we connect to Azure SQL Database<\/strong> we will see our base with the shape it had in on-premise SQL Server<\/em> and the data that her table contained.<\/p>\n\n\n\n

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

Sources:<\/h2>\n\n\n\n