Primarily a tech blog, with the possibility of some gaming and music thrown in
Previous Post in Series: Part 1: Azure Stack Deployment Guide (Updated)
Welcome back folks. So…with all the work we’ve done thus far, we’re now in a position to deploy the MSSQL RP. This will allow you to provide SQL databases as a service, so PaaS!
Here’s a list of what we’re going to do in this section of the guide:
Hello again folks, if you’ve been following this blog since it launched, you’ll be aware that I’ve been writing a series I’m calling the Server 2016 Features Series. Part of this series is exposing the Shielded VM capability to the Windows Azure Pack portal. I’m working on the assumption that some people may never have deployed WAP before, and so decided to put a guide together for it. As this guide isn’t technically part of the above series, I’ll also be including the components required for a successful minimal viable deployment of WAP Express (single server). Here is a high level of the tasks covered:
As I was about to start deploying a SQL server for use by VMM, I was reminded about how SQL is licensed when it’s for the purpose of hosting System Center databases. If you’re licensing your Hyper-V hosts with Cloud Platform Datacentre licenses, any SQL licences required for your System Center DBs are already covered.
With that in mind, I decided that if this was actually a production build, I’d build out a 2 node SQL AlwaysON cluster that uses Availability Groups for hosting all System Center databases.
The only database we will place here (during the guide) is the VMM database. For reasons I’ll explain a little further on, I had to go with the Enterprise edition of SQL, be aware though that only SQL Standard licensing is covered when using the Cloud Platform Datacentre licensing model for System Center.
Continue reading “Part 1: Deploy SQL Server 2016 Availability Groups”