Skip to main content

Azure: How to choose right SQL option that fits for your Data Migration Strategy


Choosing a right SQL deployment option is the key success for on-premises data migration journey to Cloud platform. Microsoft Azure offers distinct and highly-scalable services that fit for every data migration scenario. When it comes to SQL server data migration, Azure offers three types of deployment options namely, SQL Databases, SQL Managed Instances and SQL Virtual Machines. As a Cloud architect, if you design a migration-solution for your on-premises databases to Azure then you should get familiar with these SQL options first.

When comes to SQL server data migration, Azure offers three types of deployment options namely,

SQL Databases, SQL Managed Instances and SQL Virtual Machines.

Azure SQL Deployment Options SQL Databases SQL Managed Instances SQL Virtual Machines

However, how to decide out of these options to fit for your business or solution requirements? what key factors need to be considered while choosing the SQL option? what are the different IaaS/PaaS services offered by Azure and its capabilities? These questions must be explored with consideration of your solution requirements.
Let's read the article further to find out more in detail with my solution recommendations and use-cases explained.

Features at a glance

Firstly, the SQL Databases option,
  • It's a fully managed running as a hosted service in PaaS instance.
  • As we know, the PaaS is built on standardized hardware and software that is owned, hosted and fully managed by Microsoft, so the best part is it comes with in-built capabilities like auto scaling, 99.99% availability, backup and restore and so.
  • Microsoft takes care of everything hence only less administration may be required from consumers.
  • It offers up to 100 TB of storage for a single database.
Next, let’s look at the features of SQL Managed Instances,
  • It’s kind of a standard SQL version that we generally use on-premises.
  • As it runs on PaaS infrastructure, so comes with inbuilt support to auto scale, high availability and backup features like SQL databases.
  • It is an instance that can hold up to 100 databases and you can cross querying between them directly. It gives 8 TB as Maximum instance reserved storage
  • It does support running the SQL jobs.
  • It offers BYO-hybrid licensing for your on-premise products and discounted pricing for dev/test environments.
  • It can be connected through a Private IP address within Azure Vnet.
Finally, let’s look at the features of SQL Virtual Machines,
  • SQL VM instance is an IaaS cloud model, that means with this option you can get full control on the VM and its underlying OS, attached storage as well.
  • It supports running SQL job agents.
  • Allows BYOL license versions of the VM images and offers Up to 256 TB of storage.
  • It may require high administration basically for configuring, hosting and managing a database. However, it is specifically optimized for migrating on-premise applications to Azure hybrid deployments.

A Key Question

With consideration of all the features discussed above, you should also find the answer to a key question below. 
Remember! The answer is a key driver to your data migration.

Decision Factors Summary

The decision on choosing the SQL option clearly depends on various factors. From a solution architectural perceptive, here are some key factors to think about before deciding a migration approach.

The SQL databases option is best for modern cloud applications, this option should be considered 
  • if the application requires latest stable SQL features and advanced cloud offerings
  • when the organization is already familiar with Platform as a service (PaaS) model.
The SQL managed instances option is best for most migrations to the cloud, this option should be considered,
  • for lift-and-shift with 100% migration compatibility 
  • if application requires multi database mode with cross querying feature 
  • if the application wants to enable SQL jobs 
  • when an organization thinks it's time to cloud and market.
The SQL virtual machines option is best for migrations, this option should be considered
  • when an application requiring OS level access
  • when organization thinks time to cloud and also to simulate an AS-IS environment
  • as an easier and quicker migration approach compared to other SQL deployment options.
As a final note, 
In addition to the above key factors, a detailed technical fitment analysis also should be done before finalizing any SQL option in order to realize other non-functional requirements such as data security, performance, high-availability, backup, fail-over and so. This would help you to make a more informed decision on finalizing the data migration strategy.

Find this blog insightful? Share your comment.

Happy Solutioning!!
Labels:

Comments

Sharmila said…
Its quite interesting to learn the features and chooe the Azure SQL Options for our requirements
Apr 17, 2020, 10:04:00 PM
Post a Comment

Popular posts from this blog

How to Implement Lombok in IntelliJ for Java Projects: A Step-by-Step Guide

Lombok in IntelliJ for Java Projects Implementing Lombok in your Java project can streamline your code by reducing boilerplate. Follow these steps to set up Lombok in IntelliJ: Step 1 :  Ensure Java SDK Version. Ensure that your project is using Java 8 or higher.  You can check and set the Java SDK version in pom.xml: XML <properties> <maven.compiler.source>1.8</maven.compiler.source> <maven.compiler.target>1.8</maven.compiler.target> </properties> Step 2 : Add Lombok Dependency to pom.xmlOpen the pom.xml file in your project. Add the following Lombok dependency inside the <dependencies> section: XML <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <version>1.18.24</version> <scope>provided</scope> </dependency> Step 3 : Download Lombok Plugin for IntelliJ IDEAGo to File > Settings (or press Ctrl+Alt+S). Navigate to Plugins. Search for Lombo...
Post a Comment
Read more

How to implement JUnit 5 in Your Maven or Gradle Project: A Step-by-Step Guide for Java Testing

Unit Testing JUnit Learn how to integrate JUnit 5 in your Maven or Gradle project for efficient Java testing. This guide covers adding dependencies, creating test classes, writing test methods, and running tests in IntelliJ IDEA and Visual Studio Code to ensure robust and error-free code. Step 1: Create a Simple Java Application Create a simple Java application, for example, “Copilot Demo,” and select Maven or Gradle as the build system through IntelliJ IDEA or Visual Studio Code. Step 2: Add JUnit Dependency For Maven: Add the following dependency to your pom.xml file inside the <dependencies> tag: XML <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-engine</artifactId> <version>5.11.2</version> <scope>test</scope> </dependency> For Gradle: Add the following dependencies to your build.gradle file: dependencies { testImplementation 'org.junit.jupiter:junit-jupiter-engine:5.11.2' } Step ...
Post a Comment
Read more

How to Set Up SonarQube in IntelliJ: A Step-by-Step Guide

SonarQube in IntelliJ: (Looking for SonarLint then check here:  How to install and execute Sonarlint ) Setting up SonarQube in IntelliJ can significantly enhance your code quality by identifying bugs and vulnerabilities. Follow these steps to integrate SonarQube with IntelliJ: Step 1 :  Install SonarLint PluginOpen IntelliJ and navigate to Settings. Go to Plugins > Marketplace. Search for SonarLint, install it, and restart the IDE. Step 2 : Configure SonarLint Click on SonarLint at the bottom left of IntelliJ. Select Configure SonarLint. In the popup, check the box for Bind project to SonarQube/SonarCloud and click on Configure the connection. Step 3 :  Set Up the ConnectionIn the new popup, click the + icon to add a new connection. If the + icon is not visible, go to File > Settings > New UI and disable it. Apply changes and restart the IDE. Name your connection and select SonarQube. Enter the SonarQube URL (e.g., https://sonar.prod.company.com) and click Next....
Post a Comment
Read more