DP-070T01:

Introduction to open
source database migration
on Azure

© Copyright Microsoft Corporation. All rights reserved.

 L01 – MySQL, MariaDB, and PostgreSQL database services in Azure

Agenda L02 – Considerations for migration

L03 – Approaches to migration

© Copyright Microsoft Corporation. All rights reserved.

Lesson 01
MySQL, MariaDB, and PostgreSQL database
services in Azure

© Copyright Microsoft Corporation. All rights reserved.

Lesson Objectives
By the end of this lesson, you will understand how to:
• Decide whether to use an Infrastructure-as-a-Service approach or a Platform-as-a-
Service approach to host a database server in the cloud.
• Describe features of Azure Database for MySQL, Azure Database for MariaDB, and
Azure Database for PostgreSQL.
• Choose whether to run a MySQL, MariaDB, or PostgreSQL database on Azure virtual
machines or containers.

© Copyright Microsoft Corporation. All rights reserved.

Overview of Azure as a database platform
Advantages realized by using databases in the cloud.

Availability Scalability IaaS PaaS

• Azure includes physical

• Guaranteed SLAs • You can scale quickly • Azure includes
hardware
• No need to manage • You can respond to hardware, operating
• You configure virtual
fault-tolerant hardware peaks in demand systems, and software
machines, operating
• Azure implements • You can reduce • You control the
systems, software, and
resilience capacity rapidly databases
databases

© Copyright Microsoft Corporation. All rights reserved.

What are the Azure Database services for MySQL,
MariaDB, and PostgreSQL?
Azure Database Azure Database Azure Database
for MySQL for MariaDB for PostgreSQL

• High availability • Predictable performance and scaling

• Predictable performance • Secure data and high availability
• Scaling • Automatic backups and PITR
• Secure data • Security and compliance
• Automatic backups and PITR Deployment options:
• Security and compliance • Single server or Hyperscale (Citus)

© Copyright Microsoft Corporation. All rights reserved.

IaaS options for MySQL, MariaDB, and PostgreSQL in Azure

Reasons to use IaaS:

• You want to control the operating systems and software
• You want to match your on-premises architecture

Choose an image from the Azure Marketplace

Use virtual machines Some images include PostgreSQL, MariaDB, or MySQL
Connect using RDP or SSH

Containers share an operating system with the host

Use containers Containers are smaller and faster to load than virtual machines
Use Kubernetes to manage large numbers of containers

© Copyright Microsoft Corporation. All rights reserved.

Review Questions

Q01 – You want to create a highly-available database system which requires the minimum of
administrative time to run. Should you use an IaaS or a PaaS approach?
A01 – Use a PaaS approach. For example, run a PostgreSQL database using Azure Database
for PostgreSQL.

Q02 – You want to run a MySQL database in an IaaS environment in which you can create
new instances as quickly as possible. Should you use virtual machines or containers?
A02 – Use containers. Because containers share an operating system with the host, they are
smaller and can start more quickly than virtual machines.

© Copyright Microsoft Corporation. All rights reserved.

Lesson 02
Considerations for migration

© Copyright Microsoft Corporation. All rights reserved.

Lesson Objectives
By the end of this lesson, you will understand how to:
• Assess dependencies and fallback requirements.
• Select the migration approach; online or offline.
• Determine the most suitable way to migrate applications that use your databases.
• Maintain parallel systems.
• Consider whether to migrate a database system in one unit or piecemeal by
workload.
• Assess security concerns.
• Determine the best way to monitor and manage your databases in Azure.

© Copyright Microsoft Corporation. All rights reserved.

Assess dependencies and fallback requirements

Investigate dependencies Prepare to fall back

© Copyright Microsoft Corporation. All rights reserved.

Offline versus online migration
Offline migrations Online migrations

1. Take the database offline, once all

transactions have completed on
Friday evening. 1. You don't take the original database
2. Take a full backup or export of the offline before taking a backup or
database. export.
3. Shut down the on-premises server 2. While the migration is in progress,
and keep it in case you need to fall changes apply to the old database.
back. 3. The migration tool ensures that
4. Restore the database on the target these changes are migrated to the
cloud system. new database before the switch
5. Bring the target system online. over.
6. Reconfigure clients to connect to
the cloud database.
Application migration
 Move applications one-at-a-time to the new database
 Move subsets of users
 Adopt a combination of both approaches
Migration
 Connect as each role
 Ensure security is configured correctly
 Verify full functionality
Regression test
 Mimic expected loading for an extended duration
 Verify throughput and response times
 Scale. Allocate additional resources as necessary
Soak test
 Select a small pool of users
 Users are connected to the new system, unawares
 Note any comments from users
Canary test
Maintaining parallel systems

Testing

Consider:
• Conflict resolution
Phased • Network traffic
• Latency

Piecemeal
Piecemeal migration

Multiple databases Single database

Security Concerns
Firewall protection
• Replicate firewall rules in the cloud

Authentication and authorization

• Create users and assign
permissions

Encryption
• Use SSL encryption
Monitoring and management

Monitoring Management

• Use existing tools • Use existing tools

• Replicate existing functionality with • Use the Azure Portal
Azure tools • Use Azure PowerShell
• Expand existing functionality with Azure • Use Azure CLI
tools
Review Questions

Q01 – Offline migration enables users to continue accessing your existing on-premises
database while data is copied to a new database in the cloud. Changes made to the existing
database while migration occurs will be automatically applied to the new database. True or
false?
A01 – True

Q02 - You want to migrate individual applications and users running specific workloads to the
cloud as in initial step in migrating your system. If this is successful, you will migrate further
workloads, until the entire system has been moved. How can you do this?
A02 – Follow a piecemeal approach to migration

© Copyright Microsoft Corporation. All rights reserved.

Lesson 03
Approaches to migration

© Copyright Microsoft Corporation. All rights reserved.

Lesson Objectives
• Export data from a on-premises system and import it into a cloud database.
• Use a backup and restore technique to migrate data into a cloud database.
• Migrate database schema, content, and security information by developing custom
code.
• Use the Azure Database Migration Service to move data.
• Consider moving data into Azure SQL Database.

© Copyright Microsoft Corporation. All rights reserved.

Export and import

Plan an export and

When to use Tools
import
• Subset of the tables Plan to migrate: • MySQL Workbench
• Database objects • The database schema • Data Export
• Data from sources • Constraints • Toad Edge
outside MySQL/ • Views, functions, • Navicat
MariaDB/PostgreSQL procedures, and triggers • mysqlimport
• User accounts and
permissions
Backup and restore

When to use MySQL/MariaDB PostgreSQL

• When you want to • mysqldump • pg_dump

migrate an entire • mysql • pg_restore
database
• When you want to make
no changes during
migration
Custom application code

• SQL Scripts generated from the database and

modified or developed from scratch.
• Compiled code from a development framework
such as .NET or Java.
• Scripts in PHP or Node.js.
• Shell scripts for Bash or PowerShell.

Flexible, but requires investment in

development time
Azure Database Migration service
Migrate MySQL to Azure SQL Database
Review Questions

Q01 – The Azure Database Migration Service automatically transfers a database

schema and data to a target database running on a service such as Azure Database
for MySQL or Azure Database for PostgreSQL. True or false?
A01 – False

Q02 - How might you migrate an on-premises MySQL database to Azure SQL
Database?
A02 – Use the SQL Server Migration Assistant

© Copyright Microsoft Corporation. All rights reserved.

Module Summary
In this module, you:
• Learned about the features and services available
in Azure for hosting an open source database.
• Learned about the key considerations for
implementing a migration project.
• Learned different approaches that you can take
for migrating databases

Next steps
After the course, review the Azure Database
content on the Microsoft website, at:

azure.microsoft.com/services/PostgreSQL
azure.microsoft.com/services/MySQL
azure.microsoft.com/services/MariaDB
© Copyright Microsoft Corporation. All rights reserved.