I wanted to share a bit about Azure SQL (PaaS) in Azure, as I believe it will commonly used by IT Pros in the future, particularly as a logging and reference databasew when working with Azure Automation. One compelling reason to Azure SQL instance of SQL Server in Azure VMs is cost. If you just need a little database, you can have what you need in Azure SQL for as little as free or a few cents a month. SQL Server in Azure VMs is going to cost the price of the VM and the SQL license if you don’t bring your own. You can read about the differences between the two at http://azure.microsoft.com/en-us/documentation/articles/data-management-azure-sql-database-and-sql-server-iaas/.
To create an Azure SQL Server instance, start by connecting to your Azure subscription in PowerShell as you normally do. If you are unsure of the steps, see http://azure.microsoft.com/en-us/documentation/articles/powershell-install-configure/.
Next, we create an Azure SQL instance as follows. This creates a new Azure SQL Server instance, with a random name chosen by Azure.
#Create Azure SQL Server $location = 'East US' $login = 'pzerger' $password = 'Pa$$w0rd!' $newSqlServer = New-AzureSqlDatabaseServer -Location $location -AdministratorLogin $login ` -AdministratorLoginPassword $password -Version "2.0"
Get the name of the Azure SQL instance name like so:
All connections to this SQL instance will be blocked by default, so you need to create a firewall rule to allow all connections. For this one, I just create a rule to allow connections from any IP address.
New-AzureSqlDatabaseServerFirewallRule -ServerName $newSQLServer.ServerName ` -RuleName "Allow all IP addresses to connect" ` -StartIpAddress 0.0.0.0 -EndIpAddress 255.255.255.255
Now we have an Azure SQL Server instance that allows connections from any IP Address. In a future post, we will connect and create a database and start making use of our resources.