SQL Server Migration
We are going to take a look at what are your different SQL server migration options, and Azure SQL deployment options. And choosing between these options, deployment options. Choosing a particular tier, and then we’ll quickly look at a Demo. All right, so quickly jumping into, what are your different sqlserver migration options available to you when you are trying to upgrade or migrate your SQL Server from one version to another. So, there are two basic ways in which you can migrate your SQL Server, the current SQL Server.
Either you decide to upgrade and modernize to Azure, and you bring your workload to Azure. Or you just decide to modernize on-premises. And you just decide to upgrade from an older version of SQL Server to a newer version of SQL Server, which is SQL Server2017 or SQL Server 2019. That’s very exciting Pretty soon. So. If you are an end of US customer, end of service customer.
You can either upgrade to a new version or you can continue to touse your EOS Server, with the help of ESU. Upgrades you can purchase those on-prem. Or when you come to Azure and you decide to modernize to Azure, and you bring your workload to VM, let’s say. You get those ESU updates for free on Azure VMS. Or you can decide to just upgrade and come to a managed instance or Azure SQL DB.
And then you never have to worry about any upgrades in the future. So looking well. Let’s dive deep into all of these options. So let’s assume that you have decided to upgrade to Azure, and modernize to Azure. And once you have decided to modernize to Azure. There are multiple options that are available to you. And the first one is SQL server virtual machines. So you want to bring your workload to Azure, but you want control over the OS, you want control over the SQL Server, and database server Complete control.
SQL Managed Instances
Then this is a good option for you. Another one SQL Managed Instances. Wherein you don’t want to manage the hardware, you don’t want to manage the OS, you don’t want to manage the database, you want Azure to manage all for you. But you want SQL Server level access and you want network access. Like, you want to make a v-net with your on-prem network and then you want to control access to that network. So Managed Instance is a good option. And the third one is SQL Databases, Azure SQL Databases. If you are trying to modernize.
It’s basically for modern cloud applications, right? When you create a database, you can easily scale it up, scale it down. It’s easy to provision and it’s for the modern workloads, modern cloud applications typical. And SQL Database also provides you a way to scale all the way up to100 terabytes and beyond. And it also lets you use options like Serverless. Where you can save some costs by not paying for computing. When you’re not using it.
You can pause in a way? – Yeah. You can pause in a way and then save some cost that way. – [Host] That’s awesome. – And there is another option. Where you can share the resources and save some cost that way also. All right. – Especially on these deployment options. Let’s say it shows something. I want all the deployment options, can you please talk about those? And also if you have some real-world examples. You can talk about those, as well. – Yeah, sounds good. So like I mentioned there are three different options available to you.
But then when to choose what, right? That’s often a source of confusion for a lot of customers. So let’s say you want to manage your SQL server. You want OS-level control, you want SQL server-level control, and you want to control everything. And so SQL Server Virtual Machine is like I mentioned, is a good option. And SQL server virtual machine typically customers also use it when they have features, they are using features like DTC and polybase.
Which are not available in Azure SQL Database, so then it becomes a natural choice for them. And also if you want to run SSIS, SSAS, SSRS type of applications. Integration services, analysis services, or reporting services Exactly. Co-locate it with your SQL Server or you want to run a third-party application, and you want to co-locate with SQL Server on Azure.
Then SQL Server VMS area good option for you. And H& R Block is one of our customers, who recently migrated their workload to SQL Server on VMS and SQL server 2017. And that was their first step of migration. And now they are looking to migrate to SQL Server Managed Instances, as their next step of migration. So once you migrate to Azure, it opens up the different ways of, you know, modernizing your application and continuously evolving them. Now let’s discuss SQL server Managed Instances.
Compatibility of Features
And Managed Instances is something that you would choose when you want 100% surface area compatibility with SQL server. So you get full compatibility of features, and you also get some control over the network. So you are allowed to create, you are able to create a v-net, and then you are able to control access to your Managed Instance through that v-net. Access, allow applications, or allow users that you want to. Komatsu is a customer who recently migrated to SQL Server Managed Instance.
They brought about 1.5 terabytes of data to Managed Instance. And they observed 49% cost savings, by migrating to Managed Instance, and 25% performance benefits. When migrating to Cloud. So they are a great, great example of managed instance migration. Now, you just want a database. You don’t want to deal with the server or instance level, and you want a database.
You want it to be fully managed. So Managed Instance also is fully managed by Azure. So you get actually all and everything, all those benefits by default, right. On SQL Database also get all these benefits by default. It’s completely managed by Azure. You just have to create a database. Spin it up, dial it up or down, according to your workload requirements. It’s very easy. Provisioning is easy, very straightforward. And it has simple deployment cycles, right. Thompson Reuters is one such customer who picked Azure SQL Database recently.
Because for the e-billing application, and they picked it because of fast provisioning, and easy scale-up and scaledown of Azure SQL Database. Now if you have an application, which is multi-tenant. When you want to host multiple databases, maybe you are selling a product to your customers, and for each of the customers, you want to host a database, in Azure SQL DB So you would. There is an option available for you,
Azure SQL DB
Which are Elastic Pools. Azure SQL DB Elastic Pools, which where you can host a multi-tenant application, and this lets you share resources among the databases. So when you do that, you can also observe some cost savings for you. So it’s a good option for those types of people, and Paychex is one such example. Who actually hosted their payment and time management software on Azure SQL Database.
And they are able to scale to tens of thousands of hundreds of thousands of customers with the help of this Azure SQL Elastic Poolmigration that they did. I see. So the next question now, is because what tier do I choose? If I let’s say I wanna go for this right here. – Yeah, that’s helpful. Like people always ask that. So we have multiple tiers available in Cloud for Azure SQL DB Managed Instance, general purposes, business-critical and Hyperscale. Hyperscale is available only for SQL DB. For SQL DB and elastic pool, we have both DTU and vcore models available. Which lets you choose.
Computing and Storage
Vcore model is basically especially, it provides flexibility to choose between computing and storage. And with hyper-scale in Azure SQL DB, you can scale very easily. You scale up and down very quickly. It’s very fast. All the way up to 200 terabytes or more. And in general-purpose here for Single or Elastic Pools we also give you our serverless option now. Which lets you save on your compute cost.
Like I mentioned before if you’re not using it. So I think Ajay is going to discuss talk about this more in detail later. And with that, I am going to just quickly give you a demo of how these all different options are available to you on Azure when you go to Azure. And how you can choose between all of these. – [Host] All right. – So let’s quickly switch to my demo screen here, and here I just have my Azure portal open. And when I come here I can go to my favorites, and now you have this new experience available to you.
A new resource type available to you just called Azure SQL So hold on. So when people go to portal.azure.com, How do they get to this screen? Let’s start really from scratch then. Yeah, so this is your portal.azure.com. You come here, you see this and you see all these resource types here. Different resource types. So if you have not seen Azure SQL before, the only resource types that you would see are probably SQL databases, SQL Managed Instances, if you have put them in favorites or virtual machines, right. And you can say create a resource here,
And if you type Azure SQL you will see a new resource type, Azure SQL, right. So I have put it in my favorites, so I see it here. Okay, now I understand. – So if I click on Azure SQL, it actually shows me it puts all the resource types together into one place now. So it actually shows me all my databases, all my VMS, and all my Managed Instances in one place. So that way I know exactly how many resources I am using.
And what all resources I have. So now let’s say if I have to, I want to add a new resource here, right? So if I click on add, it now tells me that there are these three different types of Azure SQL resources available to me. The first one is SQL Databases. Where I can pick between a single database, or elastic pool, or a hyper-scale, or a serverless. You know, different options. And the other one is Managed Instance. Where I get network-level control. So I can set up my own v-net, and the third one, of course, is SQL Virtual Machines.
Where I can bring my SQL server version from on-prem to Cloud, as is. And like I mentioned, the Eos can take benefit of the ESU. Updates for the next three years for free on Azure. So it’s a great option for customers looking to quickly migrate. So yeah these are three different options available and customers can quickly get started with their migrations with the help of these options. – That’s awesome. Thank you so much for all this great information.