Migrate Open Source Databases to Azure
Why Migrate at all?
Capacity
needs
Hardware or Cloud
OS
Data Store
Security
threats
!
Software and
hardware
refresh
Integrate
acquisitions
Datacenter
contracts expiry
End of
support
Compliance
Application
innovation
Azure Databases for PostgreSQL, MySQL and
MariaDB are fully managed, enterprise-ready
community databases-as-a-service.
Azure takes the admin out of MySQL and MariaDB
Greater manageability and security
Improved performance and intelligence
Global scalability
Built-in tools and resources
Datacenter
management
Hardware
O/S provision
/patching
Database provision/
Patch/Scaling
Virtualization
Data
Applications
High availability
/DR/Backups
Datacenter
management
Hardware
Virtualization
O/S
Database provision/
Patch/Scaling
Data
Applications
High availability
/DR/Backups
Data
Applications
Datacenter
management
Hardware
Virtualization
O/S
Database provision/
Patch/Scaling
High availability/
DR/Backups
Intelligent
performance
Intelligent security
On-premises
PostgreSQL, MySQL
and MariaDB
IaaS
Azure VMs
with
PostgreSQL, MySQL,
and MariaDB
PaaS
Azure Database
for PostgreSQL,
MySQL, and
MariaDB
Managed by Microsoft
Managed by customer
Machine learning capability
Azure Database Open Source Databases
Fully managed OSS
community databases on
MySQL, PostgreSQL,
MariaDB
Integrates Azure services
with streamlined provisioning
and management experience for
common OSS frameworks and
languages
Secure and compliant with
Advanced Threat Protection
and Azure IP Advantage
Best total cost
of ownership
with built in HA
Enterprise-ready
Easy migration Developer productivity
Built-in intelligence
optimizes performance
and security
Enterprise scale
with Hyperscale
Scale PostgreSQL databases
across 100s of nodes with
Hyperscale (Citus)
PostgreSQL, MySQL and Maria DB migration to PaaS
• Focus on your App and free yourself database
management by migrating on-premises and IaaS
PostgreSQL/ MySQL/ MariaDB workloads to
Azure Database for PostgreSQL,
Azure Database for MySQL,
Azure Database for MariaDB
• Take advantage of Azure’s enterprise-ready
features on security, compliance, and intelligent
performance
• Choose the migration approach that best fits
the needs of your customer’s workloads*
• Reduce downtime on critical databases with
Azure Database Migration Service
Ideal for migrating on-premises or IaaS to
Azure Open Source Database Services
Options for migrating to Azure Database for PostgreSQL
Discover and
assess
Connect to
Azure with your
favorite tool
Migrate schema
and data
Azure Database
Migration Service
Import/Export
Dump and store
DMS
Continuous
Sync
X
Remediate
apps
Optimize
Test
Two options to migrate to Azure Opensource Databases
Option 1
Azure Database Migration Service*
Minimize downtime with continuous sync
Recommended for full database migrations
and in-production applications
Option 2
Proof of concept migration
Use dump and restore or import/export for
faster migrations
Recommended for testing and proof of
concept scenarios only
mysqldump + restore
*Azure Database Migration Service is only available on Azure Database for MySQL
Recommended approach
Minimize downtime using Database Migration Service
1. Migrate initial load
2. New transactions continue to replicate to target
until data catches up
3. Stop new traffic coming in (downtime started)
4. Wait for last batch of data to catch up
5. Complete DB migration
6. Update connection string (back online) DMS Continuous Sync
• HarvestMark migrated its existing PostgreSQL database to
Microsoft Azure Database for PostgreSQL​in just two hours
• During the migration there was no impact to their customers.
• HarvestMark saw a 20 percent decrease in cloud hosting service
costs.
• The company maintains its high standards for reliability and
speed with Azure.
HarvestMark chooses Azure
over Amazon for improved
security and performance
Customers of HarvestMark wanted them to find a new
cloud-services provider that would avoid a conflict of
interest and give them the performance and peace of
mind for their solutions
GeekWire is serves 2 million
readers worldwide with
Azure Database for MySQL
• Based in Seattle, Washington, GeekWire is a rapidly
growing technology news site with a global readership.
As its popularity and site traffic increased, so did
performance concerns. GeekWire decided to migrate its
WordPress site to the Microsoft Azure platform.
• This ensured better scalability and performance
• Removed pain of patching, scaling, and backing up the
database and allowed them to focus on their application
• By taking advantage of fully managed service Azure
Database for MySQL the company can scale on-demand
while cutting costs 45 percent.
Summary
By Migrating to Azure Open Source
Database services customers can:
• Reduce cost and database management
• Focus on Application development
• Ensure cloud scale and performance
• Take advantage of enterprise ready
features on Azure OSS Database
• Migrating to Azures Open Source
Databases
• Seamless migration with support for
latest Open Source Database editions
• Fast and secure migration with minimal
down time
Database Migration Guide
http://aka.ms/datamigration
Azure Database Migration Service Migrate
with minimum downtime
http://aka.ms/get-dms
Resources for migration
Microsoft Azure
On-premises
workloads
Azure Database
Migration Service
© Copyright Microsoft Corporation. All rights reserved.
Partner Partner Solution Capabilities & Experience Country Availability OCP Catalog Listing Co-Sell Status Partner Contact
RecordPoint Azure Database for PostgreSQL Net new app dev; App innovation/replat Australia, USA, UK RecordPoint In Market
Simon.Harloff@recordpoint.com
Satalyst Pty LTD
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift; Net new app dev; App
innovation/replat
Australia MySQL and PostgreSQL database
migration to Azure database
In Market Todd.Elliott@satalyst.com
Kangaroot BVBA
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift; Net new app dev
Belgium, Netherlands,
Luxemburg
Open Source Databases in Azure Co-Sell Prioritized
Peter Dens
peter@kangaroot.net
Oktabit S.A. Azure Database for MySQL App innovation/replat Greece Sybil In Market antonis.papaioannou@oktabit.gr
Rockplace
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift; Net new app dev; App
innovation/replat
Korea OSS on Azure Co-Sell Prioritized kdkim@rockplace.co.kr
Actiglobal
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift; Net new app dev; App
innovation/replat
Mexico Data Platform Optimization, Adminis
tration, and Configuration
In Market
OMAR VIVES SARMIENTO
ovives@actiglobal.com
Syone SA Azure Database for MySQL
Lift and shift; Net new app dev; App
innovation/replat
Portugal, Spain, Belgium,
Norway, Sweden
MySQL / MariaDB on Azure In Market tiago.fonseca@syone.com
Ascent Technology
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift
S Africa
Opensource DB on Azure Co-Sell Prioritized richard.field@ascent.tech
10th Magnitude
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift; Net new app dev; App
innovation/replat
USA 10vu Azure Migration Co-Sell Ready
Jason Rook
jrook@10thmagnitude.com
Credera
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift; Net new app dev; App
innovation/replat
USA Azure Migration Factory Co-Sell Ready
John Franks
jfranks@credera.com
DB Best Technologies
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift; Net new app dev; App
innovation/replat
USA Data Estate Modernization Co-Sell Ready
Zach Barlow
Zach@dbbest.com
Neal Analytics, LLC Azure Database for MySQL
Lift and shift; Net new app dev; App
innovation/replat
USA, Mexico, Canada End to End Data Estate Moderniz
ation
In Market
David Brown
davidb@nealanalytics.com
Pactera Technologies
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift; Net new app dev; App
innovation/replat
USA, China, India
Website Listing in process mahesha.shivappa@pactera.com
Pragmatic Works
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift USA, CA Azure Data Platform Pilot Co-Sell Prioritized
Robert Beatty
RBeatty@pragmaticworks.com
SNP Technologies Inc
Azure Database for MySQL
Azure Database for PostgreSQL
Lift and shift; Net new app dev; App
innovation/replat
USA MySQL Migration to Azure Co-Sell Prioritized
Sachin Parikh
sachin@snp.com
OSS Databases on Azure Partners
Internal use only
The following partners have solutions in market with Azure Database for MySQL and/or PostgreSQL. They are ready to be brought into customer
engagements, workshops, demand gen campaigns, etc.
Objection handling
Objection Response
Will I end up paying more with
managed service if I’m moving form
IaaS or on-premises?
No, you will most likely pay less. IaaS and on prem servers are traditionally over built to handle spikes in workload.
Azure Database Services for MySQL and MariaDB allow you to provision in line with your typical workloads but offer the
ability to scale-up on the fly as workloads increase. HA is built in with no need for extra replicas.
Will I need to rebuild my app?
No, Azure Database Services are built around the community database engines of MySQL and MariaDB. If your app
works outside of Azure, moving to Azure will be painless.
Will I be able to move off of Azure?
Yes, by utilizing the community versions of MySQL and MariaDB you will not be locked into the service and can leave
Azure with community tools
Why should I choose Azure for my
workloads vs. Amazon, Google, and
others?
Competitor cloud vendors not offer indemnification of intellectual property for open source workloads. Microsoft offers
the Azure IP Advantage program to protect against lawsuits.
How difficult will it be to move my app
to the cloud?
No code changes are necessary to move existing applications to Azure IaaS. Zero downtime is achievable by doing an
online migration using Azure Database Migration Services.
MICROSOFT CONFIDENTIAL
MySQL homepage: http://aka.ms/mysql
MariaDB homepage: http://aka.ms/mariadb
MySQL documentation: http://aka.ms/mysqldocs
MariaDB documentation: https://aka.ms/mariadbdocs
Ask Questions: AskAzureDBforMySQL@service.microsoft.com
AskAzureDBforMariaDB@service.microsoft.com
MySQL Videos: https://aka.ms/mysql-azure-videos
MariaDB Videos: https://aka.ms/mariadb-azure-videos
Content - Azure Database for MySQL
Azure service page:
http://aka.ms/postgresql
Documentation: Azure Database for PostgreSQL
Discussion forum: MSDN, StackOverflow
Feedback forum: User Voice
Hands-on Lab: http://aka.ms/postgresqlhol
GitHub repo:
https://github.com/Azure/azure-postgresql
Content – Azure Database for PostgreSQL
Old slides
MIGRATION APPROACH
W H AT TO D I S C O V E R TO O L S F O R D I S C O V E R Y
 Application Details: Multi-Tenant, SaaS
 Identify workloads move together
 Cores, IOPS, # of DBs and Size
 Environment topology
 Replication Details
 Monitoring and Logging
 OLTP and OLAP details
 Third Party applications
 Custom fields
 Data encrypted?
 Sharding and Partitioning details
 Encoding details (UTF 8/16?)
 HA and DR details
 Back up and Retention
 PII data stored? Type of PII data
 Compliance details (ex: GDPR, HIPPA)
 PCI complaint? Financial data?
 Performance and response times
 MAP Microsoft Assessment and Planning Toolkit:
Inventory, assessment Download Link: MAP Tool kit
 Azure Migrate for application workloads and
dependencies.
 Ora2Pg: scans Oracle Databases and collects schema,
Data.
 Download | Documentation
 Inventory collection template –click Icon
O U TC O M E S O F D I S C O V E R Y
 Discover the server, application, and database assets
of different sources to PostgreSQL.
 Determine application dependencies.
 Workloads that need to be migrated together
(Server, Application, Databases).
 Inventory collection template filled.
 Ora2Pg preliminary inventory details.
DISCOVERY
ASSESSMENT
W H AT TO A S S E S S TO O L S F O R A S S E S S M E N T
 Review and Assess output of Azure migration
assistant and Azure Migration output
 Assess application technologies and target
remediation SKUs, dependency map with application,
server, DBs.
 Run and gather output from Ora2Pg
 Identify Application and Databases breaking and
critical changes. For ex: Third party application that
does not support movement to Azure, functions,
Package body and nested procedure calls ,
Synonyms, Table sub-partitions etc.
 Map the discovered inventory with limitations of
Azure PostgreSQL. For ex: Storage  IOPS
 Review LOBS, XML, JSON types
 Data load frequency.
 HA/DR- possible configurations and cost assessment
 Table partitioning, Indexes, Ingestion record sizes
 Realtime analytical workload scenarios.
 Data Encryption.
 Experience from previous migration using Ora2Pg
can convert 80-90% schema and 50% of code for
 Application Assessment Azure Migrate
 Assessment link|
Download the Migration Assistant for your .NET
and PHP Apps
 Database Assessment Ora2Pg
 Download | Sample Assessment:
 Migration Guide and
Migration Journey and Tools Video
O U TC O M E S O F A S S E S S M E N T
 Target SKUs For ex: single server Vs Hyperscale (see
next slide for sample key decision drivers)
 Target topology- Application, DB, storage, sizing,
network requires, back ups, monitoring, security,
logging, analytics, optimization and Modernize
options post migration, replication (geo Vs local),
back up and retention, storage size, application
remediation areas, code changes, function
changes/re-write code paths, Deployment and
cutover plan
 Decision to leave some DBs On-prem and move
Migrate to Azure
Database PostgreSQL
(Hyperscale)
ASSESSMENT : SAMPLE DECISION DRIVERS
Assessment and
Tools Output
Azure Database for
PostgreSQL (Single Server)
Scale beyond single node:
Multi-Tenant and SaaS
Applications?
Is customer currently on
AWS/Using Hyperscale?
Y/N
No
Yes
Concurrency: Require Faster
Response times? Parallel
queries?
Ingest terabytes of data + DB
Sizes > 100 GB?
Functions and Sub functions
require are complex and sub
sec response times?
OLTP with high volumes +
Real-time analytical workloads?
+ Analyze data in Realtime?
Horizontal scale out by
sharding across different
nodes?
P
e
r
f
o
r
m
a
n
c
e
s
c
a
l
e
M I G R AT I O N S Y N O P S I S TO O L S F O R M I G R AT I O N
 Provision resources based on target topology
identified in Assessment phase
 Create NSG rule and network pre-requisites for
migration
 Run Ora2Pg or DMS
 Migrate schema, Data
 Remediate application code to talk to new platform
 Remediate DB code that cannot be converted by tool
(Ora2Pg/ DMS)
 Create Azure DMS configuration and network re-
pre-requisites
 Identify non-breaking code and objects that are not
migrated and converted and form post-remediation
plan.
 Create optimization report.
 Azure Database Migration Service (DMS)
 Migrate to PostgreSQL |
Migrate RDS PostgreSQL
 DMS| DAMT Tool Kit
 Known Issues for online migrations
 Database Migration using Ora2Pg
 Download | Sample Assessment:
O U TC O M E S O F M I G R AT I O N
 Schema and data migrated
 Application migrated and remediated
 Cutover plan completed (Online Vs Offline
migrations)
 Sanity and smoke testing completed.
 Ready to perform testing and validation
MIGRATION
P O S T - M I G R AT I O N S Y N O P S I S B E S T P R AC T I C E S
After migration it is important to use an iterative
optimization process to ensure the best performance
and functionality of your solution in the target
environment
Verification:
 Verify the schema and Data
 Application connectivity and post migration
remediations
Optimization oppurtunities:
 Optimize with configuration changes identified
during Assessment phase and look for key indicators
 Look for resource contention
 Database performance using
pg_stat_statements module
 Check links in best practice section if you are
using Pgbench for testing performance
 Use Azure Advisor for Azure deployments
 Concurrency : Optimizing Autovaccum: Optimizing
autovacuum
on Azure Database for PostgreSQL server
 Bulk Inserts:
Optimizing bulk inserts and use of transient data on
 Performance Best Practices
 Performance Optimization Recommendations
 Tuning Best Practices
 Query Store Best Practices
 Monitoring Azure DB for PostgreSQL
O U TC O M E S O F O P T M I Z AT I O N
 Azure database for PostgreSQL performing at desired
level with no memory, CPU resource contentions and
configured as advised in the above artifacts and links
 Optimized client applications suit to modern
platform.
For additional information, refer to the following
resources.
Manage your cloud spend with transparency and
accuracy using Azure Cost Management.
Save with Azure Offers: Take advantage of offers from
Azure, such as Azure Hybrid Benefit and
Azure Reserved Virtual Machine Instances, and continue
right-sizing your migrated virtual machines to your
workloads for improved value.
Secure and manage: Help protect and manage your
POST-MIGRATION

Migrate Open Source Databases to Azure.pptx

  • 1.
    Migrate Open SourceDatabases to Azure
  • 2.
    Why Migrate atall? Capacity needs Hardware or Cloud OS Data Store Security threats ! Software and hardware refresh Integrate acquisitions Datacenter contracts expiry End of support Compliance Application innovation
  • 3.
    Azure Databases forPostgreSQL, MySQL and MariaDB are fully managed, enterprise-ready community databases-as-a-service. Azure takes the admin out of MySQL and MariaDB Greater manageability and security Improved performance and intelligence Global scalability Built-in tools and resources Datacenter management Hardware O/S provision /patching Database provision/ Patch/Scaling Virtualization Data Applications High availability /DR/Backups Datacenter management Hardware Virtualization O/S Database provision/ Patch/Scaling Data Applications High availability /DR/Backups Data Applications Datacenter management Hardware Virtualization O/S Database provision/ Patch/Scaling High availability/ DR/Backups Intelligent performance Intelligent security On-premises PostgreSQL, MySQL and MariaDB IaaS Azure VMs with PostgreSQL, MySQL, and MariaDB PaaS Azure Database for PostgreSQL, MySQL, and MariaDB Managed by Microsoft Managed by customer Machine learning capability
  • 4.
    Azure Database OpenSource Databases Fully managed OSS community databases on MySQL, PostgreSQL, MariaDB Integrates Azure services with streamlined provisioning and management experience for common OSS frameworks and languages Secure and compliant with Advanced Threat Protection and Azure IP Advantage Best total cost of ownership with built in HA Enterprise-ready Easy migration Developer productivity Built-in intelligence optimizes performance and security Enterprise scale with Hyperscale Scale PostgreSQL databases across 100s of nodes with Hyperscale (Citus)
  • 5.
    PostgreSQL, MySQL andMaria DB migration to PaaS • Focus on your App and free yourself database management by migrating on-premises and IaaS PostgreSQL/ MySQL/ MariaDB workloads to Azure Database for PostgreSQL, Azure Database for MySQL, Azure Database for MariaDB • Take advantage of Azure’s enterprise-ready features on security, compliance, and intelligent performance • Choose the migration approach that best fits the needs of your customer’s workloads* • Reduce downtime on critical databases with Azure Database Migration Service Ideal for migrating on-premises or IaaS to Azure Open Source Database Services Options for migrating to Azure Database for PostgreSQL Discover and assess Connect to Azure with your favorite tool Migrate schema and data Azure Database Migration Service Import/Export Dump and store DMS Continuous Sync X Remediate apps Optimize Test
  • 6.
    Two options tomigrate to Azure Opensource Databases Option 1 Azure Database Migration Service* Minimize downtime with continuous sync Recommended for full database migrations and in-production applications Option 2 Proof of concept migration Use dump and restore or import/export for faster migrations Recommended for testing and proof of concept scenarios only mysqldump + restore *Azure Database Migration Service is only available on Azure Database for MySQL Recommended approach
  • 7.
    Minimize downtime usingDatabase Migration Service 1. Migrate initial load 2. New transactions continue to replicate to target until data catches up 3. Stop new traffic coming in (downtime started) 4. Wait for last batch of data to catch up 5. Complete DB migration 6. Update connection string (back online) DMS Continuous Sync
  • 8.
    • HarvestMark migratedits existing PostgreSQL database to Microsoft Azure Database for PostgreSQL​in just two hours • During the migration there was no impact to their customers. • HarvestMark saw a 20 percent decrease in cloud hosting service costs. • The company maintains its high standards for reliability and speed with Azure. HarvestMark chooses Azure over Amazon for improved security and performance Customers of HarvestMark wanted them to find a new cloud-services provider that would avoid a conflict of interest and give them the performance and peace of mind for their solutions
  • 9.
    GeekWire is serves2 million readers worldwide with Azure Database for MySQL • Based in Seattle, Washington, GeekWire is a rapidly growing technology news site with a global readership. As its popularity and site traffic increased, so did performance concerns. GeekWire decided to migrate its WordPress site to the Microsoft Azure platform. • This ensured better scalability and performance • Removed pain of patching, scaling, and backing up the database and allowed them to focus on their application • By taking advantage of fully managed service Azure Database for MySQL the company can scale on-demand while cutting costs 45 percent.
  • 10.
    Summary By Migrating toAzure Open Source Database services customers can: • Reduce cost and database management • Focus on Application development • Ensure cloud scale and performance • Take advantage of enterprise ready features on Azure OSS Database • Migrating to Azures Open Source Databases • Seamless migration with support for latest Open Source Database editions • Fast and secure migration with minimal down time
  • 11.
    Database Migration Guide http://aka.ms/datamigration AzureDatabase Migration Service Migrate with minimum downtime http://aka.ms/get-dms Resources for migration Microsoft Azure On-premises workloads Azure Database Migration Service
  • 12.
    © Copyright MicrosoftCorporation. All rights reserved.
  • 13.
    Partner Partner SolutionCapabilities & Experience Country Availability OCP Catalog Listing Co-Sell Status Partner Contact RecordPoint Azure Database for PostgreSQL Net new app dev; App innovation/replat Australia, USA, UK RecordPoint In Market Simon.Harloff@recordpoint.com Satalyst Pty LTD Azure Database for MySQL Azure Database for PostgreSQL Lift and shift; Net new app dev; App innovation/replat Australia MySQL and PostgreSQL database migration to Azure database In Market Todd.Elliott@satalyst.com Kangaroot BVBA Azure Database for MySQL Azure Database for PostgreSQL Lift and shift; Net new app dev Belgium, Netherlands, Luxemburg Open Source Databases in Azure Co-Sell Prioritized Peter Dens peter@kangaroot.net Oktabit S.A. Azure Database for MySQL App innovation/replat Greece Sybil In Market antonis.papaioannou@oktabit.gr Rockplace Azure Database for MySQL Azure Database for PostgreSQL Lift and shift; Net new app dev; App innovation/replat Korea OSS on Azure Co-Sell Prioritized kdkim@rockplace.co.kr Actiglobal Azure Database for MySQL Azure Database for PostgreSQL Lift and shift; Net new app dev; App innovation/replat Mexico Data Platform Optimization, Adminis tration, and Configuration In Market OMAR VIVES SARMIENTO ovives@actiglobal.com Syone SA Azure Database for MySQL Lift and shift; Net new app dev; App innovation/replat Portugal, Spain, Belgium, Norway, Sweden MySQL / MariaDB on Azure In Market tiago.fonseca@syone.com Ascent Technology Azure Database for MySQL Azure Database for PostgreSQL Lift and shift S Africa Opensource DB on Azure Co-Sell Prioritized richard.field@ascent.tech 10th Magnitude Azure Database for MySQL Azure Database for PostgreSQL Lift and shift; Net new app dev; App innovation/replat USA 10vu Azure Migration Co-Sell Ready Jason Rook jrook@10thmagnitude.com Credera Azure Database for MySQL Azure Database for PostgreSQL Lift and shift; Net new app dev; App innovation/replat USA Azure Migration Factory Co-Sell Ready John Franks jfranks@credera.com DB Best Technologies Azure Database for MySQL Azure Database for PostgreSQL Lift and shift; Net new app dev; App innovation/replat USA Data Estate Modernization Co-Sell Ready Zach Barlow Zach@dbbest.com Neal Analytics, LLC Azure Database for MySQL Lift and shift; Net new app dev; App innovation/replat USA, Mexico, Canada End to End Data Estate Moderniz ation In Market David Brown davidb@nealanalytics.com Pactera Technologies Azure Database for MySQL Azure Database for PostgreSQL Lift and shift; Net new app dev; App innovation/replat USA, China, India Website Listing in process mahesha.shivappa@pactera.com Pragmatic Works Azure Database for MySQL Azure Database for PostgreSQL Lift and shift USA, CA Azure Data Platform Pilot Co-Sell Prioritized Robert Beatty RBeatty@pragmaticworks.com SNP Technologies Inc Azure Database for MySQL Azure Database for PostgreSQL Lift and shift; Net new app dev; App innovation/replat USA MySQL Migration to Azure Co-Sell Prioritized Sachin Parikh sachin@snp.com OSS Databases on Azure Partners Internal use only The following partners have solutions in market with Azure Database for MySQL and/or PostgreSQL. They are ready to be brought into customer engagements, workshops, demand gen campaigns, etc.
  • 14.
    Objection handling Objection Response WillI end up paying more with managed service if I’m moving form IaaS or on-premises? No, you will most likely pay less. IaaS and on prem servers are traditionally over built to handle spikes in workload. Azure Database Services for MySQL and MariaDB allow you to provision in line with your typical workloads but offer the ability to scale-up on the fly as workloads increase. HA is built in with no need for extra replicas. Will I need to rebuild my app? No, Azure Database Services are built around the community database engines of MySQL and MariaDB. If your app works outside of Azure, moving to Azure will be painless. Will I be able to move off of Azure? Yes, by utilizing the community versions of MySQL and MariaDB you will not be locked into the service and can leave Azure with community tools Why should I choose Azure for my workloads vs. Amazon, Google, and others? Competitor cloud vendors not offer indemnification of intellectual property for open source workloads. Microsoft offers the Azure IP Advantage program to protect against lawsuits. How difficult will it be to move my app to the cloud? No code changes are necessary to move existing applications to Azure IaaS. Zero downtime is achievable by doing an online migration using Azure Database Migration Services. MICROSOFT CONFIDENTIAL
  • 15.
    MySQL homepage: http://aka.ms/mysql MariaDBhomepage: http://aka.ms/mariadb MySQL documentation: http://aka.ms/mysqldocs MariaDB documentation: https://aka.ms/mariadbdocs Ask Questions: AskAzureDBforMySQL@service.microsoft.com AskAzureDBforMariaDB@service.microsoft.com MySQL Videos: https://aka.ms/mysql-azure-videos MariaDB Videos: https://aka.ms/mariadb-azure-videos Content - Azure Database for MySQL
  • 16.
    Azure service page: http://aka.ms/postgresql Documentation:Azure Database for PostgreSQL Discussion forum: MSDN, StackOverflow Feedback forum: User Voice Hands-on Lab: http://aka.ms/postgresqlhol GitHub repo: https://github.com/Azure/azure-postgresql Content – Azure Database for PostgreSQL
  • 17.
  • 18.
  • 19.
    W H ATTO D I S C O V E R TO O L S F O R D I S C O V E R Y  Application Details: Multi-Tenant, SaaS  Identify workloads move together  Cores, IOPS, # of DBs and Size  Environment topology  Replication Details  Monitoring and Logging  OLTP and OLAP details  Third Party applications  Custom fields  Data encrypted?  Sharding and Partitioning details  Encoding details (UTF 8/16?)  HA and DR details  Back up and Retention  PII data stored? Type of PII data  Compliance details (ex: GDPR, HIPPA)  PCI complaint? Financial data?  Performance and response times  MAP Microsoft Assessment and Planning Toolkit: Inventory, assessment Download Link: MAP Tool kit  Azure Migrate for application workloads and dependencies.  Ora2Pg: scans Oracle Databases and collects schema, Data.  Download | Documentation  Inventory collection template –click Icon O U TC O M E S O F D I S C O V E R Y  Discover the server, application, and database assets of different sources to PostgreSQL.  Determine application dependencies.  Workloads that need to be migrated together (Server, Application, Databases).  Inventory collection template filled.  Ora2Pg preliminary inventory details. DISCOVERY
  • 20.
    ASSESSMENT W H ATTO A S S E S S TO O L S F O R A S S E S S M E N T  Review and Assess output of Azure migration assistant and Azure Migration output  Assess application technologies and target remediation SKUs, dependency map with application, server, DBs.  Run and gather output from Ora2Pg  Identify Application and Databases breaking and critical changes. For ex: Third party application that does not support movement to Azure, functions, Package body and nested procedure calls , Synonyms, Table sub-partitions etc.  Map the discovered inventory with limitations of Azure PostgreSQL. For ex: Storage  IOPS  Review LOBS, XML, JSON types  Data load frequency.  HA/DR- possible configurations and cost assessment  Table partitioning, Indexes, Ingestion record sizes  Realtime analytical workload scenarios.  Data Encryption.  Experience from previous migration using Ora2Pg can convert 80-90% schema and 50% of code for  Application Assessment Azure Migrate  Assessment link| Download the Migration Assistant for your .NET and PHP Apps  Database Assessment Ora2Pg  Download | Sample Assessment:  Migration Guide and Migration Journey and Tools Video O U TC O M E S O F A S S E S S M E N T  Target SKUs For ex: single server Vs Hyperscale (see next slide for sample key decision drivers)  Target topology- Application, DB, storage, sizing, network requires, back ups, monitoring, security, logging, analytics, optimization and Modernize options post migration, replication (geo Vs local), back up and retention, storage size, application remediation areas, code changes, function changes/re-write code paths, Deployment and cutover plan  Decision to leave some DBs On-prem and move
  • 21.
    Migrate to Azure DatabasePostgreSQL (Hyperscale) ASSESSMENT : SAMPLE DECISION DRIVERS Assessment and Tools Output Azure Database for PostgreSQL (Single Server) Scale beyond single node: Multi-Tenant and SaaS Applications? Is customer currently on AWS/Using Hyperscale? Y/N No Yes Concurrency: Require Faster Response times? Parallel queries? Ingest terabytes of data + DB Sizes > 100 GB? Functions and Sub functions require are complex and sub sec response times? OLTP with high volumes + Real-time analytical workloads? + Analyze data in Realtime? Horizontal scale out by sharding across different nodes? P e r f o r m a n c e s c a l e
  • 22.
    M I GR AT I O N S Y N O P S I S TO O L S F O R M I G R AT I O N  Provision resources based on target topology identified in Assessment phase  Create NSG rule and network pre-requisites for migration  Run Ora2Pg or DMS  Migrate schema, Data  Remediate application code to talk to new platform  Remediate DB code that cannot be converted by tool (Ora2Pg/ DMS)  Create Azure DMS configuration and network re- pre-requisites  Identify non-breaking code and objects that are not migrated and converted and form post-remediation plan.  Create optimization report.  Azure Database Migration Service (DMS)  Migrate to PostgreSQL | Migrate RDS PostgreSQL  DMS| DAMT Tool Kit  Known Issues for online migrations  Database Migration using Ora2Pg  Download | Sample Assessment: O U TC O M E S O F M I G R AT I O N  Schema and data migrated  Application migrated and remediated  Cutover plan completed (Online Vs Offline migrations)  Sanity and smoke testing completed.  Ready to perform testing and validation MIGRATION
  • 23.
    P O ST - M I G R AT I O N S Y N O P S I S B E S T P R AC T I C E S After migration it is important to use an iterative optimization process to ensure the best performance and functionality of your solution in the target environment Verification:  Verify the schema and Data  Application connectivity and post migration remediations Optimization oppurtunities:  Optimize with configuration changes identified during Assessment phase and look for key indicators  Look for resource contention  Database performance using pg_stat_statements module  Check links in best practice section if you are using Pgbench for testing performance  Use Azure Advisor for Azure deployments  Concurrency : Optimizing Autovaccum: Optimizing autovacuum on Azure Database for PostgreSQL server  Bulk Inserts: Optimizing bulk inserts and use of transient data on  Performance Best Practices  Performance Optimization Recommendations  Tuning Best Practices  Query Store Best Practices  Monitoring Azure DB for PostgreSQL O U TC O M E S O F O P T M I Z AT I O N  Azure database for PostgreSQL performing at desired level with no memory, CPU resource contentions and configured as advised in the above artifacts and links  Optimized client applications suit to modern platform. For additional information, refer to the following resources. Manage your cloud spend with transparency and accuracy using Azure Cost Management. Save with Azure Offers: Take advantage of offers from Azure, such as Azure Hybrid Benefit and Azure Reserved Virtual Machine Instances, and continue right-sizing your migrated virtual machines to your workloads for improved value. Secure and manage: Help protect and manage your POST-MIGRATION

Editor's Notes

  • #7 I have a retail application hosting on on-premise MySQL or Postgres or MariaDB. I setup DMS pipeline to start the migration to move data from source which is my on-premise to target which is Azure Database for MySQL or Postgres. Under the hood, what DMS is doing is migrating the initial load to target. Any new transactions that come in after the initial load will continue to replicate to target until data catches up on the target side. When the developer is satisfied with the data being sync on the target, what he will do is to stop new traffic from coming into the application. Usually he or she will set the application on maintenance mode, and this stops the new transactions from coming in. We will wait for DMS to catch up and replicate the last batch of data. At this point, target is completely in-sync with the source. Developer will complete the database migration in DMS side and simply update the connection string of the application and point to Azure. There you have it! Your application now is running live pointing to Azure Database for Postgres or MySQL.
  • #9 https://customers.microsoft.com/en-us/story/geekwire https://aka.ms/kjqu8y\ Based in Seattle, Washington, GeekWire is a rapidly growing technology news site with a global readership. In addition to covering the latest innovation, GeekWire serves the Pacific Northwest tech community with events, a job board, startup resources, a weekly radio show, and more. As its popularity and site traffic increased, so did performance concerns.
  • #11 Migration guide Provides prescriptive guidance on how to do migrations. Customers have access to case studies of migrations that other customers already did. Customers will also find a list of partners that they can contact to get assistance to do migrations. DMS As organizations look to optimize their IT infrastructure to have more time and resources to focus on business transformation, Microsoft is committed to accelerating these initiatives. The new Azure Database Migration Service (DMS) is a fully managed, first party Azure service that enables seamless and frictionless migrations from heterogeneous database sources to Azure Database platforms with minimal downtime. This service will streamline the tasks required to move existing competitive and SQL Server databases to Azure. Seamlessly migrate on-premise databases at scale Experience near zero downtime for mission critical applications Trust in a robust, resilient service for every migration scenario Migrate multiple database sources to Azure *Using DMS to migrate MySQL to Azure Database for MySQL will be at private preview during Azure Database for MySQL GA. Migrate with minimum migrations Uploading a large amount of data to the cloud takes some time. Customers cannot always tolerate to stop the application while the database is being migrated. Both DMS and Attunity Replicate For Microsoft Migrations allow customers to migrate with minimum application downtime. The way it works is: while the migration is happening, the data - that users change when using the application- is replicated to the target. The mount of application downtime that customers take is reduced to the time it takes them to points the application to the target (change the connection string, change the definition of the DMS alias…).