Microsoft is doubling down on Azure SQL Database Managed Instances (DMI) this year. There are some amazing Microsoft offers to provide a Platform-as-a-Service for running SQL Server on Azure. More importantly, there is a much higher degree of capability with DMI than what is available with Azure SQL Database DTU and vCore service levels. In this blog post, you will discover the most important reasons for migrating to Azure SQL Database Managed Instances. Also, you will learn how DB Best experts can help you get there within a short period of time.
Azure SQL Database Managed Instances is a new deployment model of Azure SQL Database. It provides near 100% compatibility with the latest SQL Server on-premises (Enterprise Edition) Database Engine, Azure SQL Database Managed Instances provide a native virtual network (VNet) implementation that addresses common security concerns, and a business model favorable for on-premises SQL Server customers. Azure SQL Database Managed Instances allows existing SQL Server customers to lift and shift their on-premises applications to the cloud with minimal application and database changes. At the same time, Azure SQL Database Managed Instances preserves all PaaS capabilities (automatic patching and version updates, automated backups, high-availability), that drastically reduces management overhead and TCO.
Here are your top five reasons.
1. Microsoft is practically giving it away if you have on-premises SQL Server Enterprise Agreement
Microsoft is investing in Azure. In their opinion, the Cloud is the future of computing and they want to stake their claim. For those who are running on-premises SQL Servers, they’ve created a number of different promotions for companies that are looking to shift to Azure. With their new ‘hybrid-pricing’ scheme, Microsoft calculates an 80% in operational savings when using Reserved Instances. A lot of companies are still running SQL Server 2008/R2, which is losing support in the next few months. In this case, Microsoft is offering extended support for up to 3 years. All you need to do is move your legacy SQL Server 2008/R2 database into the cloud.
2. “Nearly” 100% compatible with on-premises SQL Server 2017
What’s better than a simple lift-and-shift? If you’re already running your SQL Server 2017 on-premises, then there are very few steps that you need to take in order to bring that database to the Azure cloud. If you’re looking at an upgrade of your SQL Server, then it’s easier than ever to take advantage of SQL Server 2017. As you move to the Azure cloud, you can begin to take advantage of the increased scalability, easy data management, and seamless data recovery options.
In terms of what “nearly” 100% compatible means, Microsoft has published the list of T-SQL commands that are not compatible with DMI. In many cases, incompatible statements that control Always On Availablity Groups makes sense since the DMI service handles this for you automatically. You can use the Microsoft Data Migration Assistant (DMA) to identify incompatible statements as well, but there is a gotcha. DMA only provides a static analysis of your database and many incompatible statements are likely contained in operational scripts or application code. We have ways with our own DBMSys platform to look for incompatibilities – see #5 below.
3. It’s fully managed so that you don’t have to worry about backups and patching
The biggest advantage of a DMI system is the ease of use and the fact that it’s fully managed. No longer do you or your DBA have to worry about the administrative work that comes with supervising a database. No longer do you have to continuously patch or update your SQL Server. DMI performs all these busy work tasks so you can concentrate on adding value to your organization with new services and innovations.
4. Drop dead simple to set up high availability
With a 99.9% SLA, Microsoft is putting all of their weight behind ensuring that Azure will be available for you. But what about your SQL itself? Well, it’s easier than ever to set up your high availability with Always On Failover Clusters and Always On Availability Groups. Basically, select the deployment option – done! The newest improvements to SQL Server 2017 and Azure ensures that you’re not going to have to worry about something wreaking havoc in your database because you’ll be protected with disaster recovery.
5. DB Best DMO can save you even more dough ($$$)
What’s the best way to move to the cloud? If you’re unsure about just how much work it will entail, why not get a free quote? DB Best and Microsoft have teamed up to offer you a no-risk, no commitment, free Database Management Optimization service (valued at $4,000) to explore your options for moving to Azure. With our state-of-the-art DBMSys platform, we can examine each aspect of your database and determine where you’re able to cut costs, consolidate servers, and how best to manage your data. Not only are you finding ways to cut costs, FOR FREE, you’re also able to see how healthy your database is and the best options available.
Migrating to Azure SQL Database Managed Instances (DMI) will represent a significant shift for DBAs in hosting and deploying their data. Managed Instances is looking to become the Platform-as-a-Service of choice for any business that is beginning to explore the Cloud. Microsoft’s investment into Azure DMI, as shown by their willingness to extend support for SQL 2008/R2 and their savings for customers, shows that it is how they view the future of online databases. To take advantage of everything that Microsoft has to offer, including a free, no-risk DMO worth $4,000, send us an email at firstname.lastname@example.org today.