Organizations still operating on SQL 2005 face considerable risks come April 12, 2016 when Microsoft no longer offers Extended Support. With a typical migration process of 200+ days, not including the roadmapping process, those organizations without a replacement strategy risk significantly increased support costs.
One of the first things to understand in any discussion of on-premises SQL Server databases versus a cloud-based solution is that you can use it all: Microsoft’s Data Platform leverages SQL Server technology and makes it available across physical on-premises machines, private cloud environments, third-party hosted private cloud environments, and public cloud. This enables you to meet unique and diverse business needs through a combination of on-premises and cloud-hosted deployments, while using the same set of server products, development tools, and expertise across these environments.
The below diagram illustrates the 4 scenarios for migrating off your SQL 2005 workloads:
- SQL Server on non-virtualized physical
- SQL Server in on-premises VMs (private cloud)
- SQL Server in Azure VM (public cloud)
- Azure SQL Database (public cloud)
SQL Server in Azure Virtual Machine (VM) falls into the industry category Infrastructure as a Service (IaaS) and allows you to run SQL Server inside a virtual machine in the cloud. Similar to Azure SQL Database, it is built on standardized hardware that is owned, hosted, and maintained by Microsoft. When using SQL Server in a VM, you can either bring your own SQL Server license to Azure (With Software Assurance) or use one of the preconfigured SQL Server images in the Azure portal.
Microsoft Azure SQL Database is a relational database-as-a-service, which falls into the industry category Platform as a Service (PaaS). Azure SQL Database is built on standardized hardware and software that is owned, hosted, and maintained by Microsoft. With SQL Database, you can develop directly on the service using built-in features and functionality. When using SQL Database, you pay-as-you-go with options to scale up or out for greater power.In general, these two SQL options are optimized for different purposes:
Azure SQL Database is optimized to reduce overall costs to the minimum for provisioning and managing many databases. It minimizes ongoing administration costs because you do not have to manage any virtual machines, operating system or database software including upgrades, high availability, and backups. In general, SQL Database can dramatically increase the number of databases managed by a single IT or development resource.
SQL Server running in Azure VM is optimized for extending existing on-premises SQL Server applications to Azure in a hybrid scenario or deploying an existing application to Azure in a migration scenario or dev/test scenario. An example hybrid scenario is keeping secondary database replicas in Azure via Azure Virtual Network. With SQL Server in Azure VMs, you have the full administrative rights over a dedicated SQL Server instance and a cloud-based VM. It is a perfect choice when IT has resources available to maintain the virtual machines. With SQL Server in VM, you can build a highly customized system to address your application’s specific performance and availability requirements.
Perhaps you have a vague idea of what your preferred solution should be for migrating your SQL 2005 workloads, but you’d like to cross-reference your ideas with a seasoned expert. If so, click the banner below and complete the accompanying form, and a SoftwareONE Technical Specialist will reach out to you shortly to help you roadmap your ideal solution.
Related blog posts: