SQL Server on Linux on Azure (part 1 – deployment)
- SQL Server on Linux on Azure (part 1 – deployment)
- SQL Server on Linux on Azure (part 2 – setup)
This is part 1 of 2. You can find part 2 here
While looking for an image on the Azure Marketplace, I stumbled across a new image which I just had to try out: SQL Server vNext on Red Hat
So I strapped on my Linux boots and started a deployment right from the marketplace. This is not different to any other Linux deployment on Azure. Set your SSH key, put in all your settings and off you go. The actual SQL server deployment will happen later from shell.
Interesting enough, this VM cannot be deployed in the classic way anymore. The settings are fixed on Resource Manager. Well, who would want to go old fashioned anyway…
If you’ve been working with Azure Resource Manager through the web portal before you’ll recognize most options in this and the next screen already. In the case you haven’t used or tried a linux IaaS VM before, the SSH key option might be new to you. If you don’t know how to work with private/public key pairs for login, SSH works as well with username and password, just change the selection to password. I will explain SSH and how to get to keys in a later article in more depth.
Microsoft recommends to use a DS13 or higher for performance testing and a DS2 or better for development and functional testing.
Nothing new or special on this screen either, it looks like no magic is happening before the actual deployment!
If we haven’t malconfigured anything the validation should go through. Next thing we”ll see is the good old deployment message pinned to our dashboard, telling us what it is we are deploying:
After the machine is done with deployment we just need to adjust the attached network security group (NSG), so our Red Hat Enterprise Linux based SQL Server can be reached.
If you haven’t configured NSGs before, you’ll get there through several ways. the quickest is to directly select the NSG from the Resource Group you deployed the VM to.
Afterwards select Inbound security rules from the NSG settings blade.
And then select “Add”.
Choose a meaningful name for the new rule, like “allow-sql-1433”. The good thing about SQL server is, there is already a pre-configured Service setting. Just choose MS SQL from the drop-down list and the rest of the rule will get configured automatically. Selecting other, setting the protocol to TCP and the port to 1433, will have the same result.
Now we are having a finished Red Hat Enterprise Linux 7.2 machine with one port open too many. In the next article we’ll setup Microsoft SQL Server vNext and get it up and running.