Microsoft Azure SQL Database Managed, Intelligent SQL in the Cloud text

OK, let’s try and breakdown the basic components of the cloud offering of Microsoft’s SQL Database and the various options available to you.

Be aware there are two differing version of SQL Server (SQL Server Database Engine and Azure SQL Database) offered in the Azure cloud. Really?

I Have Need of a Specific SQL Server Database Engine Feature

Well then, it might be best for you to visit this document. So le’ts say you’re a financial institution and by law you have to implement CDC (Change Data Capture), but if we have a look at the feature list…

Microsoft Azure SQL Database Feature List

Microsoft Azure SQL Database Feature List Change Data Capture Setting

Er, Single Databases are off the menu…so that first question could be, what features do we really need? Check the feature list, and what actually is acheivable.

Please also be aware that this may change and indeed even this example maybe wrong at some point, check the situation right now.

SQL Azure Database Deployment Models

There are only 3 basic models for Azure SQL Database and these being…

  1. Single Database
  2. Managed Instance
  3. Elastic Pool

It’s that easy. However, there are various flavours within each model. You can also deploy SQL Server Database Engine in an Azure VM called

  1. SQL on a Virtual Machine

So those are the four options you have. And we all love choice.

SQL Azure Database Deployment Models

1. Single Database

This really is great for if you only have one isolated database. When you create this single database you have to create a logical server and on that logical server you can add more databases onto a “database server”. This version of the database engine is Azure SQL Database.

2. Managed Instance

This is great if you have many databases stacked on an on-premise physical tin or virtual box SQL Server and would like to move it to the cloud. Use this if you need the database features of the SQL Server Database Engine. Great for new applications but if you want to move an existing on-premise application remember that you are using all of the features of the most recent version of SQL Server.

3. Elastic Pool

This is a collection of Single Databases from above. They all share the same resources, like CPU and memory. The Single Databases can be moved out of the Elastic Pool at any time. This is a great scenario for lower throughput servers with non-conficting use(r) times.

SQL Virtual Machine Deployment Model

If you want full control over your OS level access then this is the solution you require. You can use a pay-as-you-go licence or easily use an existing licence. The biggest difference between a SQL VM and either SQL Database or Managed Instances is that the client can choose when to start patching. But the downside is you have to manage the virtual machine.

So here at Sequallity, we can run out SQL Server Health Check on either Azure SQL, SQL Server On-premises or Virtual or on Azure or on Managed Instances.

Leave a Reply