ARM Script to Create SQL Resources with Approved Naming Convention and Tags

[nataliagourova]

Purpose

This script creates a sql server and an empty sql db on Azure, based on user's inputs.

To test

Download the code, navigate to the .Automation/SQL folder and run the following command in Powershell with appropriate inputs:
.\azureDeploy.ps1 -tenantId <retrieveFromTheCohortsKeyVault> -subscriptionId <retrieveFromTheCohortsKeyVault> -applicationId <retrieve'automation-sp-appid'fromKeyVault/orYourAzurelogin> -secret <retrieve'automation-sp-appsecret'from KeyVault/orYourAzurePassword> -resourceGroupName testnsc-rg-dev-usw2-thursday -administratorLogin testnsc-admin-usw2-thursday -administratorLoginPassword Password123A$!@-location westus2 -serverName testnsc-sqlsrv-dev-usw2-test-thursday -sqlDBName testnsc-sqldb-dev-usw2-thursday -createdBy <yourName> -creatorsEmail <yourEmail>

You can choose to create a new resource group (rg), or point to the existing rg. Creation of the resource will not overwrite the resources already in the rg. Please delete all resources after testing.
It does take a while to create the server and db, you may need to give the script good 5mins to run.
When the script is done running, check the resource group and observe the server and db resources created.

To create an operational db, when a templateDB is available (in this case, nsc-sqldb-dev-usw2-thursday) in one of the Azure resource groups, this simple script may be run in PowerShell to create a brand new db and copy contents of the existing templateDB to a brand new db the script will create. Note: the script does not work for population of existing empty db resources:

$sourceResourceGroupName = "nsc-rg-dev-usw2-thursday”   
$targetResourceGroupname = "testnsc-rg-dev-usw2-thursday”
$sourceServerName = "nsc-sqlsrv-dev-usw2-thursday"
$targetServerName = "testnsc-sqlsrv-dev-usw2-thursday"
$targetDatabaseName = <"Any-new-name">
$sourceDatabaseName = "nsc-sqldb-dev-usw2-thursday"

New-AzSqlDatabaseCopy -ResourceGroupName $sourceResourceGroupName -ServerName $sourceServerName -DatabaseName $sourceDatabaseName -CopyResourceGroupName $targetResourceGroupname -CopyServerName $targetServerName -CopyDatabaseName $targetDatabaseName

DATE	ACTIVITY	TIME
2/09	Review ARM documentation on Microsoft's site	2 hr
2/11	Created issue, reviewed Sprint 1 & Sprint 3 code	2 hr
2/12	The source code from Sprint1 merged, resolved conflicts to create Sprint3 PR	3hr
2/13	Database population research and deployment	5hr
2/14	Update per reviewers comments	2hr
Total		13 hrs

[unicornsleuth]

Made a couple comments about the db name and the server name
I also think you should rename the files so that the folder is sql (lowercase) and the files are something like create_sql_server and sql_server_params or something similarly descriptive
Also, instead of using your personal username and password, you should be using the Service Principal applicationId and secret, also in the key vault.

[theKunte]

Nice update! Good work! I see you added the tags into your script and parametrized it! I removed my tags again and just added them in azure after running the script. I might add these into my ARM template later ;)

[jak-ashuraliev]

Nicely organized param!

[jak-ashuraliev]

Overall, looks good. Cleverly imported Login module, clean params, good and simple validations. Good work, Natalia!