d7e56e74d9
* Multiple VMs Availability set quick start template - initial checkin. * Add Parameters json file. * Added Metadat json and readme files * CR feedback addressed. * Update DSC resource to have absolute data disk numbers. * Updated xSqlPs DSC resource * Using WS2012 R2 image for SQL VM because of corresponding DSC resource. * Updated DSC resource for xSqlServerSetup * Fixed SqlAsset location * BugFix 12568338 - QuickStart Template<exchange-2016-non-ha> deployment has a failure on master run * Update VM size for exchange VM to Standard_D2. * Add a step to install .Net3.5 in the DSC configuration. * Use Get-NetAdapter instead of hardcoding Net adapter name * Fix for not to use hardcoded name for net adapter. * Fixed the command |
||
|---|---|---|
| .. | ||
| Readme.md | ||
| azuredeploy.json | ||
| azuredeploy.parameters.json | ||
| deploySqlStandalone.json | ||
| deploySqlStandalone.ps1.zip | ||
| metadata.json | ||
| sqlVmTemplate.json | ||
Readme.md
Create a SQL Server 2014 Stand alone with PowerShell DSC Extension
This template will create a SQL Server 2014 Always On Availability Group using the PowerShell DSC Extension it creates the following resources:
- A Virtual Network
- Two Storage Accounts
- One external load balancer
- One VM configured as Domain Controller for a new forest with a single domain
- One VM configured as SQL Server 2014 stand alone
The external load balancer creates an RDP NAT rule to allow connectivity to the first VM created, in order to access other VMs in the deployment this VM should be used as a jumpbox.
Notes
-
The images used to create this deployment are
- AD - Latest Windows Server 2012 R2 Image
- SQL Server - Latest SQL Server 2014 on Windows Server 2012 R2 Image
-
The image configuration is defined in variables - details below - but the scripts that configure this deployment have only been tested with these versions and may not work on other images.
Deploying from Portal
- Login into Azurestack portal
- Click "New" -> "Custom" -> "Template deployment"
- Copy conent in azuredeploy.json, Click "Edit Tempalte" and paste content, then Click "Save"
- Fill the parameters
- Click "Create new" to create new Resource Group
- Click "Create"
Deploying from PowerShell
Download azuredeploy.json and azuredeploy.azurestack.parameters.json to local machine
Modify parameter value in azuredeploy.azurestack.parameters.json as needed
Allow cookies in IE: Open IE at c:\Program Files\Internet Explorer\iexplore.exe -> Internet Options -> Privacy -> Advanced -> Click OK -> Click OK again
Launch a PowerShell console
Change working folder to the folder containing this template
# Add specific Azure Stack Environment
$AadTenantId = <Tenant Id> #GUID Specific to the AAD Tenant
Add-AzureRmEnvironment -Name 'Azure Stack' `
-ActiveDirectoryEndpoint ("https://login.windows.net/$AadTenantId/") `
-ActiveDirectoryServiceEndpointResourceId "https://azurestack.local-api/" `
-ResourceManagerEndpoint ("https://api.azurestack.local/") `
-GalleryEndpoint ("https://gallery.azurestack.local/") `
-GraphEndpoint "https://graph.windows.net/"
# Get Azure Stack Environment Information
$env = Get-AzureRmEnvironment 'Azure Stack'
# Authenticate to AAD with Azure Stack Environment
Add-AzureRmAccount -Environment $env -Verbose
# Get Azure Stack Environment Subscription
$SubName = <Subscription Name> # The sbuscription name is the offer name by default
Get-AzureRmSubscription -SubscriptionName $SubName | Select-AzureRmSubscription
#Resource group name. Please make sure the resource group does not exist
$resourceGroupName = "sqlResourceGroup"
$deploymentName = "SqlDeployment"
$location = "Local"
New-AzurermResourceGroup -Name $resourceGroupName -Location $location
#Start new Deployment
New-AzurermResourceGroupDeployment -Name $deploymentName -ResourceGroupName $resourceGroupName `
-TemplateParameterFile .\azuredeploy.azurestack.parameters.json -TemplateFile .\azuredeploy.json