In Windows Server 2016, Microsoft have implemented a strong security concept called Shielded Virtual Machines. Shielded VMs have been improved in the Windows Server 2019 release. In the second part of this series, Nicolas describes what Shielded Virtual Machines are and how to configure them using PowerShell.
Because it is important with maintaining Virtual Machine environments to be able to repeat routine tasks completely accurately, Windows PowerShell has grown in importance for the job. Now you can manage the Hyper-V environment via PowerShell without needing to use the Hyper-V Manager console. It opens up many opportunities for automation.
There are unique considerations that apply to virtual machines that run SQL Server workloads in such environments. This document provides insight into considerations and best practices for running SQL Server in Hyper-V Dynamic Memory configurations on Windows Server.
A Hyper-V replica will provide a rapid disaster-recovery by simply replicating to a standby site a VM running at the primary site. Is it, therefore, ideal for running SQL Server in high-availability? Well, it depends on the type of HA you require, and whether you need the features that aren't supported.
Creating a private SQL Server VAP will reduce the time it takes to deploy additional SQL Server machines in your environment.
In his previous article “Hyper-V, an introduction” Jaap Wesselius explained about the Hypervisor, the parent partition, the child partition, and Integration Components. In this article Jaap discusses installing Hyper-V, all kinds of Virtual Hard Disks, Virtual Networks, and some best practices.