Azure SQL family of SQL Server database engine products in the cloud are : Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VM.. in the demo ,and I said we are going to work with Azure SQL single database ,a service in azure .

So first let’s understand what is SQLas a service and than see how to do the migration .

What is a single database in Azure SQL Database?

The single database resource type creates a database in Azure SQL Database with its own set of resources and is managed via a server. With a single database, each database is isolated and portable. Each has its own service tier within the DTU-based purchasing model or vCore-based purchasing model and a guaranteed compute size.
You can build your first app on a small, single database at low cost in the serverless compute tier or a small compute size in the provisioned compute tier. You change the compute or service tier manually or programmatically at any time to meet the needs of your solution. You can adjust performance without downtime to your app or to your customers. Dynamic scalability enables your database to transparently respond to rapidly changing resource requirements and enables you to only pay for the resources that you need when you need them.

Single databases and elastic pools

A single database can be moved into or out of an elastic pool for resource sharing. For many businesses and applications, being able to create single databases and dial performance up or down on demand is enough, especially if usage patterns are relatively predictable. But if you have unpredictable usage patterns, it can make it hard to manage costs and your business model. Elastic pools are designed to solve this problem. The concept is simple. You allocate performance resources to a pool rather than an individual database and pay for the collective performance resources of the pool rather than for single database performance.

Transact-SQL differences

Most Transact-SQL features that applications use are fully supported in both Microsoft SQL Server and Azure SQL Database. For example, the core SQL components such as data types, operators, string, arithmetic, logical, and cursor functions, work identically in SQL Server and SQL Database. There are, however, a few T-SQL differences in DDL (data-definition language) and DML (data manipulation language) elements resulting in T-SQL statements and queries that are only partially supported (which we discuss later in this article).

 Create the database .

So ,first of all we are going to open the azure portal and than we are going to look for SQL databases and we are going to create a new one (in order to create a database we need to have a  Server )

As you can see in the pictures above , we need to give a database name and select an existing server or create a new server. The connection string and credentials will be based on the server.

For our sample we don’t need to have elastic pool .

Elastic pools provide a simple and cost effective solution for managing the performance of multiple databases within a fixed budget. An elastic pool provides compute (eDTUs) and storage resources that are shared between all the databases it contains. Databases within a pool only use the resources they need, when they need them, within configurable limits. The price of a pool is based only on the amount of resources configured and is independent of the number of databases it contains.

For the Compute and storage we are going to work with the basic plan Which is almost free (4.99 USD/month) .

Data Migration Assistant

Now , we need to download and install Data Migration Assistant from the official link .

Now in order to start our migration we need to follow a couple of steps .

We need to create a new project and give it a name, later we need to choose from where we are migrating to where ,in our case from sql server to azure sql databse as in the picture above .

Later we need to give the connection string from both ,sql server and the azure sql database in order to do the migration .

For more details , you can follow the steps as in the video below .

When you create new resources , you need to choose where are you going to host those resources ,and here we talk about the region .

It is very important to choose were you are going to host your resources , for example let’s say you have created a backend for your service in France and you have created the Front-End (web app ) in East Asia .

well from this point we can see that you may encounter high latency issue because the Front-End and the backend are in deferent areas  more than that , you should consider saving money $$ too .

Saving Money

By comparing regions within your desired “area” as illustrated in picture below, the savings over a quantity of instances can be significant. Good region selection is fundamental to controlling Azure costs, and for costs across the other clouds as well.

simple calculation : 0.92*720hours (brazil south) =662.4$ , 
0.68(canada central) *720=489.6 $

You might move resources to different Azure regions to:

• Align to a region launch: Move resources to a newly introduced Azure region that wasn’t previously available.
• Align for services/features: Move resources to take advantage of services or features that are available in a specific region.
• Respond to business developments: Move resources to a region in response to business changes, such as mergers or acquisitions.
• Align for proximity: Move resources to a region local to your business.
• Meet data requirements: Move resources to align with data residency requirements, or data classification needs.
• Respond to deployment requirements: Move resources that were deployed in error, or move in response to capacity needs.
• Respond to decommissioning: Move resources because a region is decommissioned.

What resources can I move across regions?

Using Resource Mover, you can currently move the following resources across regions:

• Azure VMs and associated disks
• NICs
• Availability sets
• Azure virtual networks
• Public IP addresses
• Network security groups (NSGs)
• Internal and public load balancers
• Azure SQL databases and elastic pools

How to ?

To move resources across regions, you select the resources that you want to move. Resource Mover validates those resources, and resolves any dependencies they have on other resources.

In this demo we are going to move a SQL-Server and databases from East-US to France .

What we already have ?

We have a SQL-Server that contain a database and that database contain one table .
This SQL server is East-US and we have been asked to move it to France central .

PS : Do not forget to Update database connection strings before you commit.

Follow the steps below to migrate your resources from region to region .

Here we create the resource group where we are going to migrate our resources.

Here we are going to start the moving process :

• In Move resources > Source + destination, select the source subscription and region.
• In Destination, select the region to which you want to move the resources. Then click Next.

• In Resources to move, click Select resources.
• In Select resources, select the resources. You can only add resources supported for move. Then click Done.