Comparing Installation Options Available for SQL Server on Azure VM

SQLServerF1

In the below mentioned previous post, we have discussed about different installation options available for SQL Server on Azure VM
Different Installation Options Available for SQL Server on Azure VM
It is important to understand the differences in the three option mentioned in the above post.
– Create a SysPreppedImage of the SQL Server version of our choice on an hyper-v VM on out local environment and then Upload it to Azure.
– Create a virtual machine running Windows from the Azure portal and then install SQL Server on it.
– Provision a SQL Server virtual machine in Azure from the Azure portal.

SysPreppedImage of the SQL Server on Hyper-V VM and Upload to Azure is preferred when you want to use your own licenses for Windows Operating System and SQL Server, so that you only need to pay for Azure compute and storage costs incurred for hosting your VM with SQL Server on Azure. Since SQL Server 2008 R2, has introduced of performing a SysPrep image, and the steps are simple. In this DBAs can choose and install required SQL Server versions and patches and required Operating System versions and patches instead of depending up on the versions provided by Microsoft Azure. However this is the most time consuming task of the three methods as this involves buinding hyper-v VM and preparing SQL Server SysPrep image and then uploading the VHD files to the Azure and then use it to create the VM. This is preferred when you want to use your own licenses which you are have, to avoid using Microsoft licensing available for Windows OS and SQL Server from Microsoft on per-minute usage basis.

Create a virtual machine running Windows is preferred you want to use your own license of SQL Server, but use the license of Windows Operating System provided by Microsoft, however the licensing of the Windows OS usage, compute and storage usage of Azure VM are calculated on the per-minute basis. SO, In this case, we pay only for the per-minute for the Azure Compute, Storage, and Windows license but not for the SQL Server license. In this DBAs can choose and install required SQL Server versions and patches. This involves additional work of installing SQL Server, its patches.

Provision a SQL Server virtual machine in Azure is preferred when you do not want to use any of your own licenses, instead only want to dependent or use the Microsoft licenses, but this usage is mostly calculated on per-minute basis. In this we need to pay per-minute for a SQL Server license along with an Azure Compute, Storage, and Windows license. This allows us to install SQL Server at desired version and service pack level, thus reducing the time taken for SQL Server installation along with VM setup and these things can be done from Azure portal with simple clicks and providing the options. This is best suited for applications which are required for short time for testing and later can be shutdown, thus brings down the cost.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Different Installation Options Available for SQL Server on Azure VM

SQLServerF1

Cloud solutions has been gaining increased support and many customers moving their data on to cloud technologies or planning to move in future. Once management decides on moving the SQL Server on to Azure, there are two options either to choose Infrastructure as Service (IaaS) or SQL Azure database as service (PaaS). If the management decides to have more control on the SQL Server and decides to use the Infrastructure as service option(IaaS), then next step would be is to get the SQL Server installed and running on the Microsoft Azure VM. There are different ways in which we can get SQL Server installed and running on the Azure VM which depend on factors mainly like Licensing. Depending on the type of licensing we choose for, we can have below options for getting SQL Server on the Microsoft Azure VM.

– Create a SysPreppedImage of the SQL Server version of our choice on an hyper-v VM on out local environment and then Upload it to Azure.
– Create a virtual machine running Windows from the Azure portal and then install SQL Server on it.
– Provision a SQL Server virtual machine in Azure from the Azure portal.
SysPreppedImage of the SQL Server on Hyper-V VM and Upload to Azure – In this method, we can use the SQL Server SysPrep install which creates a SQL Server image, which can be used to complete and create a full SQL Server instance on any other servers. Once the SQL Server SysPrep image has been created on a hyper-v VM, next step is to upload the VHD file of the hyper-v VM to Azure Blob storage. Now we can use the uploaded VHD file and create an image from Azure Management portal.

Create a virtual machine running Windows – In this method, we can create a windows virtual machine from the Azure portal. There is an option available on Azure portal to provision a Windows Server image. Once the Windows VM is created, next step is to copy SQL Server installation media on to the newly created VM and install the SQL Server on our own.

Provision a SQL Server virtual machine in Azure – In this method, we can install SQL Server directly on a windows VM from Azure portal. This method is an easy way to get SQL Server installed on the new windows Azure VM on Microsoft Azure.

All the three methods mentioned above have their own advantages and disadvantages interms of licensing, cost, etc. Depending on the requirement, DBAs and management can choose the appropriate method best suited for their environment.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings

 

Differences Between SQL Azure Database and SQL Server in Azure VM

SQLServerF1

Microsoft is making huge investments in cloud technology and is betting big for future growth in this area. Microsoft has started providing cloud services for various products, applications, Operating System or hardware support. Based on the type of service, Microsoft has made available different offerings which include Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). Microsoft cloud support many applications or products out of which SQL Server is one of the Microsoft product which is supported on cloud by Microsoft. There are two different kind of offerings provided by Microsoft for SQL Server, which are Infrastructure as a Service (IaaS), Platform as a Service (PaaS).

Among these two services Infrastructure as a Service (IaaS), Platform as a Service (PaaS) offered by Microsoft, we a DBA or management, we need to understand what best suits our requirement and based on that we can choose the offering. It is important to understand the differences between these two offerings available for SQL Server, so that we can make an informed decision. Each offering for SQL Server from Microsoft has its own advantages and disadvantages interms if features, cost, High Availability, Disaster recovery, which operations tasks are taken care by Microsoft, etc. Below are some of the differences between SQL Azure SQL Database (PaaS) and SQL Server in Azure VM (IaaS).

SQL Azure database as service is best suited for new applications designed or optimized for cloud solutions or which depend on other cloud technologies, so that they can be used together. Developers building software-as-a-service (SaaS) applications can use Azure SQL Database to provide flexibility to support both explosive growth and profitable business models. On the other hand with Infrastructure as a Service (IaaS) is for applications which are already existing ones and cannot be changed easily and need to be migrated on to cloud without much changes to be made. Applications which are dependent on other on-premise resources are best suited for Infrastructure as a Service (IaaS) compared to SQL Azure database as service.

SQL Azure database as service does not support all features available in SQL Server and has many limitations for each feature, many of the features cannot be controlled by DBAs or developers and there is not much control for DBAs for operational tasks like patching, backups, HA or DR. Infrastructure as a Service (IaaS) is just like on-premise SQL Server instance on which DBAss or developers can make configuration changes, performs backups/restores, use required technologies for HA and DR purposes, etc. There are some limitations with SQL Azure database as service like max database size supported as of 2015 is only 500 GB, but this limitation does not apply for Infrastructure as a Service (IaaS). Another limitation include, SQL Azure database as service does not allow resources to be accessed from Azure to on-premise. Infrastructure as a Service (IaaS) does not have any such limitations.

In Infrastructure as a Service (IaaS), hardware, its maintenance costs are eliminated as it is taken care by Microsoft. SQL Azure database as service also eliminates the costs mentioned before, in addition to that, in SQL Azure database as service also eliminates maintenance and administration efforts and costs of patching, backups, HA, DR, etc. in SQL Azure database as service, there are different services available to choose for High Availability and disaster recovery where Point in Time Restore, Geo-Restore, and Geo-Replication to increase can be chosen to increase business continuity. In Infrastructure as a Service (IaaS), the High availability and disaster recovery is to be taken care by DBAs and we can choose any technology of our choice and we are responsible for administering, monitoring and fixing any problems.

Hope this was helpful.

This is applicable for below versions of SQL Server

SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server 2016

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings