Migrating SQL workloads to Microsoft Azure: Guidance and Assessment Tools

In the previous articles, Migrating SQL workloads to Microsoft Azure: Planning the jump and Migrating SQL workloads to Microsoft Azure: Services Selection, we discussed the steps that you should follow when you start thinking loudly that you need to migrate your SQL workload to Azure, by checking your on-prem site and the available services and features in Azure that meet your workload handling requirements. After that, we went through different database services provided by Azure and which one fits a specific workload, in order to make it easy for you to translate the current workload as an Azure service.

In this article, we will go through two free migration assistant tools that can be used to provide guidance steps for the migration process and assess the existing environment for any changes that should be performed before migrating the SQL workload to Microsoft Azure.

Azure Database Migration Guide

When you start drawing your plan to migrate your workload to Microsoft Azure, Azure Database Migration Guide is your first target that provides you with a comprehensive guide for designing and implementing the database workload migration process, where it provides you with all information that is required for the migration process, including all migration assistant tools and programs.

Azure Database Migration Guide can be accessed by copying the https://datamigration.microsoft.com/ address to your Internet browser, and the migration guidance page will be opened, as shown below:

Azure Database Migration Guide

The Azure Database Migration Guide supports a wide range of data sources, as shown in the previous image. This includes migrating from Microsoft SQL Server, Oracle, DB2, MySQL, PostgreSQL, MongoDB, Cassandra, MariaDB, Access, SAP ASE, and Microsoft Azure Table Storage.

In order to identify which migration targets are supported for each data source, click on that data source and choose your migration target for that data source, as below:

Migrate to

For example, you can migrate your SQL Server database to Azure SQL DB, Azure SQL MI, SQL Server on Azure VM, SQL Data Warehouse, or upgrade the current SQL Server instance.

The Azure Database Migration Guide provides us also, in the home page, with a general overview of the database workload migration process. This overview includes the pre-migration steps, such as discovering the current databases in your environment, assessing the workload, and performing the required transformation and conversion steps to meet the target schema. It also provides us with the steps that should be performed during the migration process, such as migrating the source databases to the target, synchronizing between the source and destination copy then disconnecting from the source database. Once the migration is performed, the post-migration tasks that should be performed include performing changes at the application side to connect to the new target database, testing all application functionalities and overall performance while connecting to that target database and try to optimize and fix any faced issues, as shown below:

Migration process overview

From the same home page, The Azure Database Migration Guide provides us with the list of Microsoft tools and services that can help us through the different stages of the workload migration to Microsoft Azure. It also provides us with links to the documentation of each tool, in order to guide you on how to use these tools and fix any issue you face while using these tools. These tools include:

  • Azure Migrate: that can be used for starting, executing, and tracking the Azure migration process
  • Azure Database Migration Service: that can be used to migrate multiple data sources to the Microsoft Azure database services with minimal downtime
  • Data Migration Assistant: that can be used for identifying the SQL database compatibility issues of the source databases that may affect the database functionality in the selected migration target data platform
  • SQL Server Migration Assistant: that checks the compatibility of the 3rd party source databases, such as DB2, MySQL, Oracle, and SAP ASE, with the target database platform and automate the database migration process
  • Database Experimentation Assistant: that helps in checking the target SQL Server version for a specific workload, where it will identify any query or workload that may have a compatibility or performance issue when it is migrated to the target database
  • Data Access Migration Toolkit: an extension for the Visual Studio Code tool that helps in analyzing the Java and .NET source codes and check all queries and data access calls

Microsoft migration tools and services

At the bottom of the Azure Database Migration Guide window, Microsoft provides a number of case studies from different customers, showing how they performed the migration process and the benefits gained from that migration, as shown below:

Case studies

Assume that we need guidance for migrating our on-prem SQL Server instance to Azure SQL Database. From the Azure Database Migration Guide window, click on the Microsoft SQL Server source and choose the Azure SQL Database as a target database platform, as below:

Migrate a SQL database

From the opened window, comprehensive step-by-step guide will be displayed, including the steps that should be performed before starting the migration, during the migration and after migrating the database to Microsoft Azure, as shown below:

Migrate SQL Server to Azure SQL Database

On the right side of the previous window, you can find a list of the 3rd party tools that can also be used to migrate your SQL workload to Microsoft Azure or the selected destination.

Microsoft Assessment and Planning Toolkit

The Microsoft Assessment and Planning Toolkit is a free tool that can be used to check if the current environment is ready to be migrated to the new upgraded on-prem or cloud environment. It provides us with all required inventory, assessment, and reporting resources that help when planning to migrate your SQL workload to Microsoft Azure. Microsoft Assessment and Planning Toolkit can be used to check the web applications and SQL Server instances that are installed on the current machine where the toolkit is installed or scan for multiple machines and servers that are registered under a specific Active Directory Domain.

The Microsoft Assessment and Planning Toolkit can be downloaded from Microsoft Download center, where it provides you with the ability to download the toolkit installation file, sample documentation, instructions how to use that tool, as shown below:

The Microsoft Assessment and Planning Toolkit Download

#azure #migration #sql #tools #microsoft-azure

What is GEEK

Buddha Community

Migrating SQL workloads to Microsoft Azure: Guidance and Assessment Tools
Cayla  Erdman

Cayla Erdman

1594369800

Introduction to Structured Query Language SQL pdf

SQL stands for Structured Query Language. SQL is a scripting language expected to store, control, and inquiry information put away in social databases. The main manifestation of SQL showed up in 1974, when a gathering in IBM built up the principal model of a social database. The primary business social database was discharged by Relational Software later turning out to be Oracle.

Models for SQL exist. In any case, the SQL that can be utilized on every last one of the major RDBMS today is in various flavors. This is because of two reasons:

1. The SQL order standard is genuinely intricate, and it isn’t handy to actualize the whole standard.

2. Every database seller needs an approach to separate its item from others.

Right now, contrasts are noted where fitting.

#programming books #beginning sql pdf #commands sql #download free sql full book pdf #introduction to sql pdf #introduction to sql ppt #introduction to sql #practical sql pdf #sql commands pdf with examples free download #sql commands #sql free bool download #sql guide #sql language #sql pdf #sql ppt #sql programming language #sql tutorial for beginners #sql tutorial pdf #sql #structured query language pdf #structured query language ppt #structured query language

Migrating SQL workloads to Microsoft Azure: Guidance and Assessment Tools

In the previous articles, Migrating SQL workloads to Microsoft Azure: Planning the jump and Migrating SQL workloads to Microsoft Azure: Services Selection, we discussed the steps that you should follow when you start thinking loudly that you need to migrate your SQL workload to Azure, by checking your on-prem site and the available services and features in Azure that meet your workload handling requirements. After that, we went through different database services provided by Azure and which one fits a specific workload, in order to make it easy for you to translate the current workload as an Azure service.

In this article, we will go through two free migration assistant tools that can be used to provide guidance steps for the migration process and assess the existing environment for any changes that should be performed before migrating the SQL workload to Microsoft Azure.

Azure Database Migration Guide

When you start drawing your plan to migrate your workload to Microsoft Azure, Azure Database Migration Guide is your first target that provides you with a comprehensive guide for designing and implementing the database workload migration process, where it provides you with all information that is required for the migration process, including all migration assistant tools and programs.

Azure Database Migration Guide can be accessed by copying the https://datamigration.microsoft.com/ address to your Internet browser, and the migration guidance page will be opened, as shown below:

Azure Database Migration Guide

The Azure Database Migration Guide supports a wide range of data sources, as shown in the previous image. This includes migrating from Microsoft SQL Server, Oracle, DB2, MySQL, PostgreSQL, MongoDB, Cassandra, MariaDB, Access, SAP ASE, and Microsoft Azure Table Storage.

In order to identify which migration targets are supported for each data source, click on that data source and choose your migration target for that data source, as below:

Migrate to

For example, you can migrate your SQL Server database to Azure SQL DB, Azure SQL MI, SQL Server on Azure VM, SQL Data Warehouse, or upgrade the current SQL Server instance.

The Azure Database Migration Guide provides us also, in the home page, with a general overview of the database workload migration process. This overview includes the pre-migration steps, such as discovering the current databases in your environment, assessing the workload, and performing the required transformation and conversion steps to meet the target schema. It also provides us with the steps that should be performed during the migration process, such as migrating the source databases to the target, synchronizing between the source and destination copy then disconnecting from the source database. Once the migration is performed, the post-migration tasks that should be performed include performing changes at the application side to connect to the new target database, testing all application functionalities and overall performance while connecting to that target database and try to optimize and fix any faced issues, as shown below:

Migration process overview

From the same home page, The Azure Database Migration Guide provides us with the list of Microsoft tools and services that can help us through the different stages of the workload migration to Microsoft Azure. It also provides us with links to the documentation of each tool, in order to guide you on how to use these tools and fix any issue you face while using these tools. These tools include:

  • Azure Migrate: that can be used for starting, executing, and tracking the Azure migration process
  • Azure Database Migration Service: that can be used to migrate multiple data sources to the Microsoft Azure database services with minimal downtime
  • Data Migration Assistant: that can be used for identifying the SQL database compatibility issues of the source databases that may affect the database functionality in the selected migration target data platform
  • SQL Server Migration Assistant: that checks the compatibility of the 3rd party source databases, such as DB2, MySQL, Oracle, and SAP ASE, with the target database platform and automate the database migration process
  • Database Experimentation Assistant: that helps in checking the target SQL Server version for a specific workload, where it will identify any query or workload that may have a compatibility or performance issue when it is migrated to the target database
  • Data Access Migration Toolkit: an extension for the Visual Studio Code tool that helps in analyzing the Java and .NET source codes and check all queries and data access calls

Microsoft migration tools and services

At the bottom of the Azure Database Migration Guide window, Microsoft provides a number of case studies from different customers, showing how they performed the migration process and the benefits gained from that migration, as shown below:

Case studies

Assume that we need guidance for migrating our on-prem SQL Server instance to Azure SQL Database. From the Azure Database Migration Guide window, click on the Microsoft SQL Server source and choose the Azure SQL Database as a target database platform, as below:

Migrate a SQL database

From the opened window, comprehensive step-by-step guide will be displayed, including the steps that should be performed before starting the migration, during the migration and after migrating the database to Microsoft Azure, as shown below:

Migrate SQL Server to Azure SQL Database

On the right side of the previous window, you can find a list of the 3rd party tools that can also be used to migrate your SQL workload to Microsoft Azure or the selected destination.

Microsoft Assessment and Planning Toolkit

The Microsoft Assessment and Planning Toolkit is a free tool that can be used to check if the current environment is ready to be migrated to the new upgraded on-prem or cloud environment. It provides us with all required inventory, assessment, and reporting resources that help when planning to migrate your SQL workload to Microsoft Azure. Microsoft Assessment and Planning Toolkit can be used to check the web applications and SQL Server instances that are installed on the current machine where the toolkit is installed or scan for multiple machines and servers that are registered under a specific Active Directory Domain.

The Microsoft Assessment and Planning Toolkit can be downloaded from Microsoft Download center, where it provides you with the ability to download the toolkit installation file, sample documentation, instructions how to use that tool, as shown below:

The Microsoft Assessment and Planning Toolkit Download

#azure #migration #sql #tools #microsoft-azure

Migrating SQL workloads to Microsoft Azure: Planning the jump

In this article, we will discuss several points that should be considered when planning to migrate the on-premises SQL workload to Microsoft Azure cloud services. This article is the first step in a series of articles that discuss how to perform the SQL and No-SQL workload migration smoothly to the cloud.

Why migrate?

Data is one of the most precious “assets” in each company that drives business success. And as a proactive Data Engineer in an international company, you will always think how to secure your data at rest and in transit, and use the most optimal data platform technologies to serve the data to the application clients from any point in the earth as fast as possible with the minimum downtime or data loss possibilities.

With the growth of the company business, it is your responsibility to keep track of the data storage and retrieval speed in order not to lose your clients. Put yourself in the shoes of a client who is trying to submit an online order to buy from your online store, but the site is taking a long time to refresh the content and submit the order. For me, I will close the site and buy it from the nearest store!

Loading

If the Infrastructure administrator starts complaining about the limitation in the remaining resources in the current hosting machine, or the delay in receiving the new purchased resources, it is the suitable time to discuss with the management the choice to move your SQL workload to Microsoft Azure.

SQL Cloud

Initial Study

Before you think to send a meeting request to your management to discuss your idea about migrating the current SQL workload to Microsoft Azure, you need to take into consideration that it is not only one word that you need to mention to the management or a step by step tutorial that you can follow to perform the migration process. You should be prepared and ready for any question by preparing a comprehensive study that includes the current site problems and limitations, a plan for the design and implementation phases of the migration process, and the benefits that the company will gain from moving that workload to Azure from all performance, business growth handling and cost.

The initial study for the migration process should include, but may extend:

  • The current SQL and No-SQL workload types in your company, such as OLTP and OLAP workloads
  • The database administration and monitoring tools that you are using in the on-prems site
  • The list of on-prems database engine types, versions, and locations
  • The current database resources size and the expected resources growth ratio for each database
  • The dependencies between the databases. This helps in selecting the list of candidate databases that will participate in the first migration wave and the database consolidation possibilities to reduce the cloud hosting cost
  • The dependencies between the databases and the applications and how these applications interact with the databases. This will end up grouping the databases based on its dependencies. It is better to have a discussion with the development team to identify the criticality of each database for the business and see if it is possible to migrate the database applications to Microsoft Azure
  • The different security and encryption requirements for each database
  • The backup strategy and tools used for each database
  • The list of all additional components that are involved in the data models, such as SSIS, SSAS, and SSRS that should be migrated
  • The list of issues that you are facing in the current site, such as performance or availability
  • The limitations in the current site, such as hardware upgrade limitation or unsupported features
  • The Availability requirements for your databases
  • The confirmed Restore Time Objective (RTO) and Restore Point Objective (RPO) for your databases and how they are met in the current site

Cloud Considerations

After checking the current situation, you should have a look at the cloud solutions that can be used to replace the current on-premises site. This includes learning the features available in each service and the pros and cons of each service in order to identify which service meets your requirements. With the different available cloud providers, I will concentrate on the Microsoft Azure database services in my articles, such as SQL on Azure VM, Azure SQL Database, Azure SQL Managed Instance, and Azure SQL Data Warehouse, and how to use it as a replacement for the on-premises ones.

Migrate to Cloud

Once you review the Microsoft Azure database-related services, your need to take into consideration the following points in your migration plan that may extend:

  • Choose the suitable target data platform in the cloud, Infrastructure as a Services (IaaS) or Platform as a Service (PaaS), based on your technical requirements, and cost plan. This choice specifies what Azure services can be used and the control level on these services
  • The Microsoft Azure services that can be used as a replacement for every single feature, component, or functionality in the on-prems site to serve your workloads
  • The proper size for the Microsoft Azure services to fit the current site growth ratio with the minimal possible cost. Scaling up/down plans or scaling out/in plans at that stage will be a great step ahead
  • The suitable region(s) to host each database that provides the lowest latency, based on the applications and client’s locations
  • The Availability solution that should be used in Microsoft Azure, based on the selected Azure service, to meet your database availability requirements
  • The cloud services configurations and features that can be used to meet the confirmed Restore Time Objective (RTO) and Restore Point Objective (RPO)
  • The ability to achieve the security and privacy compliance and regulatory requirements of your organization using the cloud services
  • The changes that should be performed on the current workload to be compatible with the target data platform technologies in Microsoft Azure and what transformation tools can be used to achieve that
  • The new features in the cloud that can be used to optimize the current workload
  • The administration and monitoring tools that can be used to replace the on-prems tools
  • The ability to perform the security and encryption requirements for each database
  • The backup and recovery cloud solutions can be used to design and automate the database backup strategy
  • Any potential blockers for the migration process
  • The tools that will be used to migrate the current workload to the cloud with minimal possible downtime and data loss
  • Validation test strategy by migrating sample workload and how to measure the gains and compare it with the on-premises site
  • The breaking fixes that should be performed after the migration process
  • The rollback plan in case of any single possible failure

Now you can send the invitation to your management and discuss with them if migrating the current on-premises workload to the cloud is feasible, or you need to move with upgrading the current on-premises data center to handle the workload growth, serving the clients with highest possible availability and minimal data loss, without losing the company clients or having them frustrated from the company services.

#azure #migration #sql #sql-azure #sql-server #microsoft-azure

Migrating SQL workloads to Microsoft Azure: Services Selection

In the previous article, Migrating SQL workloads to Microsoft Azure: Planning the jump, we discussed the main points that should be checked and considered while drawing your plan to migrate the SQL workload from the on-premises datacenters to Microsoft Azure. In this article, we will go through the different database services that are provided by Microsoft Azure to help you in selecting the proper service that can serve your SQL workload when migrating it to Microsoft Azure.

IaaS or PaaS

Before choosing the suitable Microsoft Azure database service that meets your requirements, you need to specify the suitable Azure platform. Microsoft Azure provides two high-level platform options: Infrastructure as a Services, also known as IaaS and Platform as a Service, also known as PaaS. The platform choice specifies the Azure services that can be used and the control that you can have over the services under that platform.

Choosing the IaaS platform, you are renting the IT infrastructure servers and virtual machines from the cloud provider. This includes storage, networks, and operating systems. With this platform, you are still responsible for and have control over the Operating System layer and all layers over the OS, including the installation of the services, the operating system patching, and so on.

On the other hand, the PaaS platform provides you with the ability of building, testing, and deploying your applications without worrying about the underlying infrastructure management. In other words, you are not responsible for installing an operating system or patching the machine with the latest security and system updates.

The following image shows your responsibilities, in light blue, and the list of layers that you don’t need to worry about, in dark blue, where the cloud service provider, Microsoft for example, is responsible for managing the tasks fall under that layer. You can see that you are responsible for everything when hosting your databases in your datacenter, requiring multiple teams to handle these tasks, which is not possible for the start-up and small companies, as shown below:

IaaS vs PaaS

Microsoft Azure Database Services

Now we are familiar with the difference between the platforms provided by Microsoft Azure. We need to identify the database services that are provided under each platform.

In the IaaS platform, you can rent a virtual machine and install your SQL Server instance in that machine, where you will be responsible for the Operating System and SQL Server installation and administration tasks under that service.

Moving to PaaS, you can see that Microsoft Azure provides you with different choices based on your workload type. For example, you can use Azure SQL Database or Azure SQL Managed Instance for your transactional SQL workload and use Azure Cosmos DB for your No-SQL transactional workload. For the analytical workload, you can use the Azure SQL Data Warehouse instance, under the Azure Synapse Analytics service.

Let us discuss each SQL database service provided by Microsoft Azure briefly.

SQL Server on Azure VM

The IaaS platform provides you with the ability to install and run your SQL Server instance in a fully managed Azure virtual machine. This option is the best choice when you plan to perform a lift-and-shift from your on-prem environment to Microsoft Azure with the minimal possible changes on your applications and databases schema, providing you with full control over the SQL Server instance and the Operating System management and security configurations, allowing you to host any number of user databases on that SQL Server VM, and provide you with the ability to configure customized high availability and disaster recovery solution.

SQL Server on Azure VM is suitable for you if your company already has IT teams to administrate that virtual machine from OS, networking, and security perspectives. And you will be billed for both the storage used to store your data and the compute operations consumed on that VM.

Rather than waiting for the purchase approval for the new hardware, you can easily, in a few minutes, deploy a new virtual machine in Azure, install a new SQL Server instance using your own license and connect to that SQL Server instance, with the ability to scale it up and down based on your requirements, and stop it during the idle time and resume it again when needed.

Azure SQL Database

Azure SQL Database, categorized under the PaaS platform, is a cloud-computing database service that provides you with the ability to host and use SQL databases in the cloud without worrying about the hardware and the software requirements. Although you are not responsible for the hardware security, the operating system patching and security, and the database files, that are encrypted at rest using the TDE feature, you are still responsible for preventing unauthorized access to the data by limiting the allowed IP addresses from the firewall side and the authorized users from the database access and permissions configuration.

Azure SQL Database provides us with many features, including the ability to automate the backup operation and keep your backup for up to 10 years, create a readable secondary replica to distribute the reporting workload to another datacenter, tune the performance automatically, Point-In-Time Restore, built-in high-availability, and the ability to scale the database resources on the fly up and down, by changing the Database Throughput Unit (DTU) value, and scale-out with no downtime, without the need to wait for any new hardware purchase order as in the on-prems scaling processes, as shown below:

Azure SQL Database

By providing the name of the database and a few other options, your database will be up and running and ready to serve your transactional workload in a few minutes. With no hardware or operating system to buy or manage, you will pay only for what you use. Feel free to use the Azure Total Cost of Ownership Calculator to estimate the cost of your PaaS service usage.

Azure SQL Database can be deployed as a single database, purchased by DTU or vCore models, with its own set of resources managed by a logical SQL Server, that can be used when the database usage is stable. It can be also deployed using an elastic pool, purchased by eDTU or vCore models, that contains a group of databases that share the same set of resources and managed by a logical SQL Server, providing the best choice for the databases with frequently changing usage patterns. If your application surface area scoped at the database level, using the Azure SQL Database is the best choice.

#azure #migration #sql #sql-server #sql-azure #microsoft-azure

Migrating SQL workloads to Microsoft Azure: Assessment and Migration Tools

In the previous articles of this series we discussed how to draw the initial strategy when planning to migrate the SQL workload to Microsoft Azure, the different database target platforms provided by Microsoft Azure that can be used as a migration target, based on the workload type, and finally, we went through some tools that help in discovering and assessing the on-premises environment by identifying the migration blocking issues and providing guidance steps for the migration process.

In this article, we will go through three new tools that can be used to assess the on-premises databases and identify any migration blocker, then migrate these databases to Microsoft Azure database service.

Microsoft Data Migration Assistant

The Data Migration Assistant (DMA) tool is used mainly to check the compatibility issues that may affect the database functionality when migrating your databases to a new SQL Server version or to Azure SQL Database. DMA helps by identifying any feature in the current version that is not supported in the new version or in the cloud, what new features in the new version we can benefit from, providing recommendations to enhance the performance and the reliability in the new version and finally migrate the on-premises version to a newer version or to Azure SQL Database.

The Data Migration Assistant can be used to assess and migrate any SQL Server installed on Windows machine with version 2005 and later, to any SQL Server instance installed on Windows or Linux with version 2012 and later or to Azure SQL Database. DMA tool is recommended as an alternative to the SQL Server Upgrade Advisor tool to assess and upgrade to the new SQL Server versions. For migrating to Azure SQL Database, it is recommended to use the Azure Migration Service instead.

The Data Migration Assistant can be downloaded from Microsoft Download center and installed to your machine, using a straight-forward installation wizard, as shown below:

DMA installation wizard

Once installed to your machine, you need to be a member of the sysadmin fixed SQL Server role in order to use that tool.

The Data Migration Assistant provides you with the ability to configure the number of databases to assess in parallel, Number of databases to migrate in parallel and the SQL connection timeout from the dba.exe.config configuration file before start using that tool. In this demo, we will use the default values for assessing and migrating without changes.

When you start the Data Migration Assistant, click on the (+) icon to create a new assessment project to check any blockers, unsupported features or recommendations before migrating your databases from on-premises site to Microsoft Azure SQL Database. You need to provide a meaningful name for the project, the type of assessment, source and destination data platforms, as shown below:

New DMA Project

In the project configuration window, specify what will be assessed in the source databases, such as any compatibility issue or unsupported features that may block the migration process, as shown below:

Assessment options

After that, you will be asked to provide the SQL Server name and the credentials that will be used to connect to that SQL Server instance, as below:

Connect to SQL Server

Once connected, all user databases hosted under that instance will be listed, providing you with the ability to choose the databases that will be assessed before migrating it to Microsoft Azure SQL Database, as shown below:

Add DB

Now the databases are ready for the assessment. Click on the Start Assessment option to assess the databases in the selected list, as shown below:

Start Assessment

Once the assessment process completed successfully, review the list of breaking points and unsupported features that are provided by the Data Migration Assistant, with the ability to save the assessment result, export it or upload it to Azure Migrate tool, as shown below:

Assessment result

Azure Database Migration Service

The Azure Database Migrate service provides you with the ability to perform online or offline database migration from a large scale of database sources, such as SQL Server, MySQL, Oracle, DB2, MongoDB and PostgreSQL, to Microsoft Azure Data platform using the Azure Portal and with the minimal downtime.

Internally, the Azure Database Migrate service uses the Database Migration Assistant tool to generate the assessment reports, providing all changes required before starting the migration process.

Before creating a new Azure Database Migration Service instance and use it to migrate the databases to Microsoft Azure, we should register the Microsoft.DataMigration resource provider.

This can be performed by opening the Azure portal and browsing the subscription under which we plan to create the Azure Database Migration Instance. From the selected subscription move to the Resources Providers option and search for Microsoft.DataMigration resource provider and register it. Once it is registered, the status will be changed to Registered, as shown below:

Microsoft.DataMigration Registeration

Now we are ready to create a new instance of Azure Database Migration Service.

#azure #migration #sql #sql-server #microsoft-azure