As discussed in the Azure cloud adoption framework (CAF) overview blog, the structure of CAF is not a linear journey and is a cycle that repeats itself as cloud adoption evolves. This blog post will provide an overview of data migration to Azure.
The below decision tree helps identify the appropriate data store(s) to use.
Common Database Scenarios
| Scenario | Data service |
| I need a globally distributed, multi-model database with support for NoSQL choices. | Azure Cosmos DB |
| I need a fully managed relational database that provisions quickly, scales on the fly, and includes built-in intelligence and security. | Azure SQL Database |
| I need a fully managed, scalable MySQL relational database that has high availability and security built in at no extra cost. | Azure Database for MySQL |
| I need a fully managed, scalable PostgreSQL relational database that has high availability and security built in at no extra cost. | Azure Database for PostgreSQL |
| I plan to host enterprise SQL Server apps in the cloud and have full control over the server OS. | SQL Server on Virtual Machines |
| I need a fully managed elastic data warehouse that has security at every level of scale at no extra cost. | Azure Synapse Analytics |
| I need data lake storage resources that are capable of supporting Hadoop clusters or HDFS data. | Azure Data Lake |
| I need high throughput and consistent, low-latency access for my data to support fast, scalable applications. | Azure Cache for Redis |
| I need a fully managed, scalable MariaDB relational database that has high availability and security built in at no extra cost. | Azure Database for MariaDB |
Azure SQL
Azure SQL is a modern platform powered by the SQL Server engine.
Azure SQL Virtual Machine
Azure SQL virtual machine, is an infrastructure as a service (IaaS)model and is best suited for lift and shift scenarios where workloads requires an operating system access or if the database is customized.
Azure SQL Managed Instance
Azure SQL Managed Instance, is a fully managed service and platform as a service (PaaS) model, and offers the latest SQL Server (Enterprise Edition) database engine.
Azure SQL Database
Azure SQL Database is a relational database as a service (DBaaS) and falls under the platform as a service (PaaS) category, and provides a single database option and a elastic pool option.
Azure SQL Comparison Table
| Azure SQL Database | Azure SQL Managed Instance | SQL Server on Azure VM |
|---|---|---|
| Supports most on-premises database-level capabilities. The most commonly used SQL Server features are available. 99.995% availability guaranteed. Built-in backups, patching, recovery. Latest stable Database Engine version. Ability to assign necessary resources (CPU/storage) to individual databases. Built-in advanced intelligence and security. Online change of resources (CPU/storage). | Supports almost all on-premises instance-level and database-level capabilities. High compatibility with SQL Server. 99.99% availability guaranteed. Built-in backups, patching, recovery. Latest stable Database Engine version. Easy migration from SQL Server. Private IP address within Azure Virtual Network. Built-in advanced intelligence and security. Online change of resources (CPU/storage). | You have full control over the SQL Server engine. Supports all on-premises capabilities. Up to 99.99% availability. Full parity with the matching version of on-premises SQL Server. Fixed, well-known Database Engine version. Easy migration from SQL Server. Private IP address within Azure Virtual Network. You have the ability to deploy application or services on the host where SQL Server is placed. |
| Migration from SQL Server might be challenging. Some SQL Server features are not available. No guaranteed exact maintenance time (but nearly transparent). Compatibility with the SQL Server version can be achieved only using database compatibility levels. Private IP address support with Azure Private Link. | There is still some minimal number of SQL Server features that are not available. No guaranteed exact maintenance time (but nearly transparent). Compatibility with the SQL Server version can be achieved only using database compatibility levels. | You need to manage your backups and patches. You need to implement your own High-Availability solution. There is a downtime while changing the resources(CPU/storage) |
| Databases of up to 100 TB. | Up to 8 TB. | SQL Server instances with up to 256 TB of storage. The instance can support as many databases as needed. |
| On-premises application can access data in Azure SQL Database. | Native virtual network implementation and connectivity to your on-premises environment using Azure Express Route or VPN Gateway. | With SQL virtual machines, you can have applications that run partly in the cloud and partly on-premises. For example, you can extend your on-premises network and Active Directory Domain to the cloud via Azure Virtual Network. For more information on hybrid cloud solutions, see Extending on-premises data solutions to the cloud. |
Choosing a deployment option
Migration tooling options
Assess
Optimize
Data security & protection
Develop clear, simple, and well-communicated guidelines to identify, protect, and monitor the most important data assets anywhere they reside.
Identify and classify sensitive assets, and define the technologies and processes to automatically apply security controls.
Once the data you need to protect has been identified, consider how you will protect the data at rest and data in transit.
Data at rest: Data that exists statically on physical media, whether magnetic or optical disk, on premises or in the cloud.
Data in transit: Data while it is being transferred between components, locations or programs, such as over the network, across a service bus (from on-premises to cloud and vice-versa), or during an input/output process.
Data Classification
Data classification process categorizes data by sensitivity and business impact in order to identify risks. When data is classified, you can manage it in ways that protect sensitive or important data from theft or loss.
The following is a list of classifications Microsoft uses. Depending on your industry or existing security requirements, data classification standards might already exist within your organization.
You can also create custom tags with the SQL classification tools in SSMS.
- Non-business: Data from your personal life that doesn’t belong to Microsoft.
- Public: Business data that is freely available and approved for public consumption.
- General: Business data that isn’t meant for a public audience.
- Confidential: Business data that can cause harm to Microsoft if overshared.
- Highly confidential: Business data that would cause extensive harm to Microsoft if overshared.
Data management
Azure Data Catalog
Azure Data Catalog is a fully managed cloud service that serves as a system of registration and system of discovery for enterprise data sources. Data Catalog allows users to provide their own descriptive metadata – such as descriptions and tags – to supplement the metadata extracted from the data source, and to make the data source more understandable to more people.
Azure Data Catalog also allows users to provide their own complete documentation that can describe the usage and common scenarios for the data source.
This wraps up the Cloud Adoption Framework – Data Migration Overview.
Thanks Abdul for sharing this. Pretty handy cheat sheet :). Crisp and clear.