Azure SQL Data Migration

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
14 hours 28 minutes
Difficulty
Intermediate
CEU/CPE
15
Video Transcription
00:00
>> Hello, Cybrarians.
00:00
Welcome to Lesson 3.2 of Module 3
00:00
>> of this course titled,
00:00
>> AZ-301, Microsoft Azure Architect Design.
00:00
Here are the learning objectives for this video.
00:00
We'll start out by covering
00:00
the tools that are available for
00:00
assessing existing SQL workloads
00:00
>> for migration to Azure.
00:00
>> We'll also cover the tools that we
00:00
can use for the Azure migration.
00:00
Then we'll cover migration scenarios that are
00:00
supported by the Azure Database Migration Service,
00:00
which is what I'll be using my demo.
00:00
Finally, we'll talk about
00:00
the options of offline migration
00:00
and online migration when
00:00
using the service. Let's get into this.
00:00
Let's talk about migrating data from
00:00
other different data sources into Azure SQL Database.
00:00
Depending on which database that we're
00:00
coming from or which databases as a source,
00:00
we have different tools that are available for us to be
00:00
able to do the assessment and then the migration.
00:00
The assessment is very important
00:00
in this case because it's when we do
00:00
the assessments that we're able to uncover
00:00
database compatibility issues and
00:00
feature parity issues that maybe
00:00
could be blockers for migration scenario.
00:00
Not all databases can be migrated to Azure SQL and
00:00
not all data bases can be migrated to
00:00
Azure SQL Managed Instance
00:00
without making any changes or any modifications.
00:00
That's where the assessment comes in.
00:00
There are different tools that are available to
00:00
help us depending on
00:00
the scenario that we're working with.
00:00
For example, if you're looking to migrate SQL Server to
00:00
Azure SQL there's a tool called
00:00
the Database Migration Assistant, DMA.
00:00
What this tool can help us to do is it can help
00:00
us to check for database compatibility.
00:00
That's going to look at our database schema it's going to
00:00
identify legacy syntax that are still in use.
00:00
Things like CLR,
00:00
non answer joins or even file streams,
00:00
which is not even supported on Managed Instance.
00:00
It's going to uncover
00:00
when those are used and it's going to
00:00
recommend different walk around or solutions to us.
00:00
It's also going to check for things like
00:00
feature parity at a database level.
00:00
If you're using things like linked servers,
00:00
if you're using SSIS packages,
00:00
which Azure SQL does not support,
00:00
there's another service in Azure called
00:00
Azure Data Factory that we're going to talk about.
00:00
If you're using an ETL jobs,
00:00
you're using SQL Server Agent jobs,
00:00
that run PowerShell script for example,
00:00
that's more supported in Azure SQL.
00:00
It's going to uncover those and highlight those to
00:00
us and give us recommendations to work around them.
00:00
One of the good things about
00:00
Database Migration Assistant is that the results can be
00:00
uploaded into a service in Azure called
00:00
Azure Migrate for centralization.
00:00
That's going to give us a holistic view
00:00
of a migration scenario.
00:00
Azure Migrate is a tool that
00:00
can help with assessment of servers and applications.
00:00
But then we can upload the result
00:00
from DMA into Azure Migrate.
00:00
We get this holistic view across servers,
00:00
applications, and databases from a single pane.
00:00
There's another tool called a
00:00
SQL Server Migration Assistant,
00:00
which has been around for a while,
00:00
which can help in scenarios like MySQL and
00:00
Oracle migration into Azure SQL.
00:00
It can help us with the assessment of this.
00:00
Actually both DMA and SSMA
00:00
can actually help in certain migration cases.
00:00
It can actually do certain migration even though it's
00:00
not the best way or the most recommended way to do that.
00:00
Recommendation is do the assessment using these tools,
00:00
but the do migration using
00:00
Azure Database Migration Service.
00:00
The other tool that I've listed there,
00:00
is a tool called Database Experimentation Assistant
00:00
that can help us with assessment.
00:00
When it comes to migration
00:00
the service that's mainly recommended by
00:00
Microsoft now is a service in Azure
00:00
called Azure Database Migration Service.
00:00
This is the service that I'll be showing you in the demo.
00:00
Let's look more closer at this service.
00:00
Azure Database Migration Service is
00:00
a service in Azure that can help us in
00:00
a migration scenarios from
00:00
different database sources into
00:00
different database targets in Azure.
00:00
For example, on the left-hand side,
00:00
you can see a list of different source
00:00
supported by Azure Database Migration Service.
00:00
At the top you can see a list of
00:00
different database targets in
00:00
Azure that are supported by the same service.
00:00
For example, let's look at some of the scenario.
00:00
If you look into migrate data into Azure SQL Database,
00:00
Azure Database Migration Service can
00:00
help us to migrate data from SQL Server,
00:00
AWS SQL and Oracle into Azure SQL Database.
00:00
If we're looking to migrate data into
00:00
Azure SQL Database Managed Instance,
00:00
it's the same cases for SQL Server,
00:00
AWS SQL and Oracle.
00:00
We're looking to migrate data into
00:00
SQL that's running on an Azure virtual machine,
00:00
SQL Server and Oracle are supported if we
00:00
look into migrate into
00:00
Azure Cosmos DB and there'll be more on this later.
00:00
It can help us to migrate from MongoDB database
00:00
into the MongoDB API of Azure Cosmos DB.
00:00
If we're looking to migrate
00:00
into Azure Database for MySQL,
00:00
it can help us to migrate data from
00:00
MYSQL databases on-premises or AWS,
00:00
MySQL into Azure Database for MySQL.
00:00
Then finally for Azure Database for PostgreSQL.
00:00
It can help by taking data from Oracle, AWS,
00:00
PostgreSQL or just native PostgreSQL
00:00
on-premises straight into Azure Database for MySQL.
00:00
When using the database migration service,
00:00
there are two scenarios that we can do with migration.
00:00
There's the offline migration scenario and
00:00
then there's the online migration scenario.
00:00
One of the things that we ought to
00:00
understand is that with online migration scenario
00:00
that's only supported by
00:00
the premium tier of the Database Migration Service.
00:00
Database Migration Service has two tiers,
00:00
the standard tier or the premium tier.
00:00
The premium tier is the only one
00:00
that support online migration.
00:00
It support both online and offline,
00:00
while standard tier only supports offline.
00:00
Now in terms of the differences between them.
00:00
With offline migration application downtime
00:00
begins when the migration starts,
00:00
and maybe this is my idea for you.
00:00
For example, when you're doing the migration,
00:00
it's probably bad for
00:00
business if your website is down because you're
00:00
migrating your data over into
00:00
Azure SQL or into any other target in Azure.
00:00
That will not be something that's good for
00:00
your reputation as a business.
00:00
When it comes to online migration on the other hand,
00:00
online migration is going to keep
00:00
data synchronized between the source and the target,
00:00
as long as the database migration service is running.
00:00
Then this allows the migration
00:00
to be done without downtime.
00:00
The minimum downtime that we may have,
00:00
will be when we actually just do the cut over and
00:00
when we're switching our connection strings.
00:00
But when DMS is run it's just keeping data
00:00
in sync between the source and the target databases.
Up Next