Edit

Support policy for Microsoft SQL Server products that are running in a hardware virtualization environment

  • Article

This article describes the support policy for SQL Server products that are running in a hardware virtualization environment.

Original product version:   SQL Server
Original KB number:   956893

Introduction

This article describes the support policy for Microsoft SQL Server products that are running in a hardware virtualization environment.

More information

Microsoft provides technical support for SQL Server for the following supported hardware virtualization environments:

  • Windows Server versions (currently in support lifecycle) with Hyper-V

  • Microsoft Hyper-V Server

  • Configurations that are validated through the Server Virtualization Validation Program (SVVP).

    For more information about certified vendors and about configurations for SVVP, see http://windowsservercatalog.com/svvp.aspx?svvppage=svvp.htm.

    Note

    The SVVP solution must be running on hardware that is certified for Windows Server version (currently in support lifecycle) to be considered a valid SVVP configuration.

Microsoft provides technical support for SQL Server versions for the following supported hardware virtualization environments:

  • Azure Infrastructure Services that includes Azure Virtual Machines, Azure Virtual Network, and Azure VMware Solution (See the Frequently asked questions section for more details).
  • The SQL Server version is currently a supported version according to the lifecycle policy.

Microsoft may provide limited or no technical support for the following environments:

  • Any version of SQL Server that is outside the lifecycle policy and running on any virtualization vendor or configuration.
  • Any non-Microsoft virtualization software that isn't a configuration that is validated through the SVVP program.

This policy of limited support is based on the following Microsoft Knowledge Base article:

Support policy for Microsoft software that runs on non-Microsoft hardware virtualization software

Restrictions and limitations

The following restrictions and limitations may affect the support policy of the above supported configurations:

  • Guest Failover Clustering is supported for SQL Server in a virtual machine for the supported hardware virtualization environments listed in this article provided all the following requirements are met:

  • The SQL Server product must be a supported version under its current Microsoft Support Lifecycle policy. For more information about Microsoft Support Lifecycle policies, see Search Product and Services Lifecycle Information.

  • SQL Server supports virtualization-aware backup solutions that use VSS (volume snapshots). For example, SQL Server supports Hyper-V backup.

    Virtual machine snapshots that do not use VSS volume snapshots are not supported by SQL Server. Any snapshot technology that does a behind-the-scenes save of a VMs point-in-time memory, disk, and device state without interacting with applications on the guest using VSS may leave SQL Server in an inconsistent state.

  • SQL Server on Hyper-V Replica is supported provided the EnableWriteOrderPreservationAcrossDisks flag is set.

    Note

    To set the EnableWriteOrderPreservationAcrossDisks flag, run the following cmdlet:

    Set-VMReplication -VMName \<vm-name> -EnableWriteOrderPreservationAcrossDisks 1

    Exceptions

    If multiple SQL VMs are tightly coupled with one another, individual VMs can fail over to the disaster recovery (DR) site but SQL high availability (HA) features inside the VM need to be removed and reconfigured after VM failover. For this reason, the following SQL Server features are not supported on Hyper-VM Replica:

    • Availability Groups
    • Database mirroring
    • Failover Cluster instances
    • Log shipping
    • Replication

    For SQL Servers running on Linux environment, review the guidance in the Supported virtualization technologies section of Technical support policy for Microsoft SQL Server.

    It is recommended to use SQL Server in Run Hyper-V in a Virtual Machine with Nested Virtualization for testing and development purposes only.

Frequently asked questions

  • Q1: What level of technical support will I receive if my non-Microsoft vendor configuration is certified through SVVP?

    A1: Microsoft Customer Service and Support (CSS) will work together with the customer and the SVVP certified vendor to investigate the problem with SQL Server that is running in the virtual machine. Microsoft CSS or the SVVP vendor will follow the process that is documented on the following SVVP website to use the TSANet program together with the customers' permission in an attempt to resolve the problem:

    Server Virtualization Validation Program

  • Q2: What if the non-Microsoft vendor virtualization configuration is not certified through SVVP?

    A2: Microsoft CSS will follow the support policies that are documented in Knowledge Base article 897615. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

    Support policy for Microsoft software that runs on non-Microsoft hardware virtualization software

    If Microsoft CSS determines that the problem may be related to the vendor virtualization software, Microsoft CSS may require the customer to reproduce the problem outside the virtualization environment.

    Not all vendor configurations are considered certified by SVVP even though the vendor participates in the program. The list of validated configurations may be updated as vendors submit changes through this program.

  • Q3: The SVVP program specifically lists the valid configurations for Windows Server 2008. Are other versions of Windows supported to be used as guest operating system?

    A3: Yes. As documented at the following SVVP website, products that have passed the SVVP requirements for the latest released version of Windows Server are considered supported on all earlier versions of Windows Server that are still supported per Lifecycle Matrix.

    Server Virtualization

    When running SQL Server on a guest operating system, the version of SQL Server must be supported on the version of the guest operating system, according to the requirements that are listed in the respective SQL Server product documentation.

    For more information about the hardware and software requirements for SQL Server, visit the following pages on docs:

  • Q4: Are SQL Server features such as database mirroring supported to run in a virtualization environment?

    A4: The only restrictions to install and use SQL Server in a virtualization environment are documented in this article or in the SQL Server product documentation. Any feature or usage that is not stated in this article or in the SQL Server product documentation is assumed to be supported in a virtualization environment by using the same restrictions and support as a bare metal hardware environment. For more information about the features that are supported by different editions of SQL Server, visit following TechNet website:

    Features Supported by the Editions of SQL Server 2008 R2

    These same requirements apply to SQL Server 2008 and later versions that are running in a virtualization environment.

  • Q5: Is Quick and Live Migration with Windows Server supported with SQL Server?

    A5: Yes, Live Migration is supported for SQL Server when used with Windows Server with Hyper-V and with Hyper-V server. Quick Migration is also supported for SQL Server in Windows Server with Hyper-V and Hyper-V Server.

  • Q6: What is the support policy for SQL Server when using an SVVP vendor virtualization feature such as snapshots or migration?

    A6: Snapshots for any virtualization vendor that do not use VSS are not supported with SQL Server. Any other virtualization additional functionality of an SVVP vendor such as migration must be supported by the SVVP vendor. This includes any problems that might occur with SQL Server when using these features. Read this resource for more information about the support policy for additional functionality of a virtualization product:

    Server Virtualization Validation Program

  • Q7: Is Hyper-V Dynamic Memory supported for SQL Server?

    A7: Hyper-V Dynamic Memory is fully supported with SQL Server. Only SQL Server versions and editions that support Hot Add Memory (Enterprise and Datacenter) can see memory that is added by using Hyper-V Dynamic Memory. SQL Server 2012 and later versions of standard edition also recognize Hot Add memory when running in a virtual environment. SQL Server versions that do not support Hot Add Memory are still supported. But these versions will detect only the memory that is present in the operating system when SQL Server starts. Before you deploy Hyper-V Dynamic Memory, please read the following resources when you use Hyper-V Dynamic Memory with SQL Server:

  • Q8: Do you support SQL Server running in Microsoft Azure Virtual Machine?

    A8: Yes, Microsoft supports SQL Server in Microsoft Azure Infrastructure Services that includes Microsoft Azure Virtual Machines and Microsoft Azure Virtual Network. Consider the following when you deploy SQL Server in Microsoft Azure Virtual Machine:

  • Q9: Does Microsoft support SQL Server running in Microsoft Azure VMware Solution?

    A9: Yes, Microsoft supports SQL Server in Microsoft Azure Infrastructure Services, which includes Microsoft Azure VMware Solution. When you deploy SQL Server in Microsoft Azure VMware Solution, consider the following resources:

  • Q10: Can customers run SQL Server in the Microsoft Azure VM role?

    A10: Microsoft Azure VM role is a non-persistent role and not the same as Microsoft Azure Virtual Machine. It's not supported for SQL Server production use. Customers who want to deploy data platform capabilities today in the Microsoft Azure platform should use Microsoft Azure Virtual Machine or Microsoft Azure SQL Database.

  • Q11 Are there any recommended configuration or best practices to consider while deploying SQL Server in virtualized environments?

    A11: Yes, you should consult with the following recommendations from the respective hypervisor: