Tech Tips, Tricks & Trivia

The figure below is a graphical representation of SQL Server availability group solution   in Azure  for HADR   consisting of the following elements: A virtual network containing multiple subnets, including a front-end and a back-end subnet Two domain controller with an Active Directory (AD) domain Two SQL Server VMs deployed to the back-end subnet and joined to the AD domain A 3-node WSFC cluster with the Node Majority quorum model An availability group with two synchronous-commit replicas of an availability database You can reduce the number of virtual machines by using a domain controller as the quorum file share witness. This would reduce the number of VMs for a two-replica availability group Related: -  Creating SQL Server 2014 Always On Availability Group in an existing Azure VNET and Active Directory instance -  SQL Server AlwaysOn Availability Groups Listener configuration with Azure External Load Balancer

My first experience using a VM was with a Virtual PC VHD that Microsoft offered to test IE. Over the years, I've worked with VMWare Player and Hyper-V virtual machines and I love the convenience they provide - so much so that whenever I start a major project, I prefer having a new VM. For those that have not experienced the joy of VMs, here is a list of its uses: * Save time on environment build-outs - building a development environment from scratch can be a time-consuming affair. With a VM ready, you can instead focus on real work and never worry about any rogue software messing up your environment. With a backup of that VM in hand, you lose no time in getting up and running again. * Testing new software without disturbing your host environment - whether its beta software or a version of a software that cannot parallely with what's already on the host OS, VMs help you play safe. * Manage hardware crunches - when you don't have the luxury or budget to have physical ...