Azure SQL Database Deployment using Azure PowerShell
Try reloading this page, or reviewing your browser settings
This video segment provides the step-by-step guidance on how to deploy an Azure SQL instance using the Azure Portal.
- Azure portal deploy setup Azure SQL instance
About this video
- Peter De Tender
- First online
- 09 August 2019
- Online ISBN
- Copyright information
- © Peter De Tender 2019
Welcome to this Azure SQL course. Where in this video, you’ll learn about deploying an Azure SQL database using the Azure portal. This section is pretty easy in structure, where I’ll start with explaining what is required to be able to deploy an Azure SQL database using the Azure portal. After which, I will show you the same using a live demo.
Now before deploying your Azure SQL database from an Azure portal perspective, you need to think about several required parameters. If you don’t know those answers or settings to those parameters, it’s not even possible to get a deployment succeeding. The required parameters to provide during a portal based deployment of Azure SQL is the SQL Server name, where the name must be unique across all Azure SQL Server instances. Which by the way, might sometimes be a challenge.
Now that uniqueness is important because every single Azure instance database is created in the name space database.windows.net. Next, like any other Azure resource you want to deploy, you need to allocate an Azure Resource Group and the Azure Region where you want to create that specific resource. Which by the way, might be a different region than where the resource group is.
Next, you also need to specify your Azure SQL sizing or cost plan settings that you want to allocate for that specific instance. And then lastly, you need to provide a name for your SQL database instance itself. And this should allow you to get the Azure SQL database deployment running.
Now, two screenshots here, but again, I’ll show you in an upcoming demo. Now from a deployment perspective, you have two options. Or you start with creating a new SQL Azure server object. And again, it’s not a virtual machine that you’re going to manage, but it’s like a SQL Server placeholder. Or combining the SQL Azure server and database deployment all from the same process.
So with that, let me walk you through the Azure SQL deployment using the Azure portal, where I’m going for the second option, deploying a database and allowing me to create that server all from the same process. So I’m connecting to my SQL Azure portal, if you want. And I’m going to create a new resource.
Out of that list which is known as Azure Marketplace, I can find the SQL database option right here. This is going to start up the Create SQL database plate where I need to provide some details. And like I mentioned in the presentation, it’s mainly about a resource group. So let me start with that part, creating a new resource group. Why not naming it the Azure SQL portal resource group and a name for my database.
Azure portal is going to validate a couple of settings here and everything looks fine. Next, it’s going to ask me for my server. Now since I don’t have a SQL Server object yet, I need to create a new one. And this is where you need to provide a new unique database server name. As again, it’s created in that database.windows.net name space. And this name seems to be OK.
Next, I’m going to provide my local admin account for managing my server later on. And as you can see, there are some requirements for a complex password. And lastly, I’m going to specify in which Azure region I’m going to deploy my database.
That little flag here– allow Azure services to access the server– could be handy, but you might need to check it from a security compliance perspective if that’s actually allowed. Because this means that all Azure services within didn’t or even without your subscription, but still within your tenant isolation, can access your database server. That should be about it.
Next, you need to specify if you want to use elastic pools. I’ll talk about it later on. And what kind of database performance options I want to use. To just allow my initial deployment, I’m going to start with one of these smallest options, and I’ll come back to the database plans later on, anyway.
Then finally closing my creation preparation step and kicking off my deployment. This will run for about 2, 3 minutes, and then we can check back if everything is up and running. And with that, after only a few minutes, we have a successful deployment.
So if you go back to the resource groups, checking that Azure SQL portal resource group, we have a SQL Server object up here and an empty SQL database. And with that, I’m really through the core topic of what I wanted to cover here, showing you and explaining what it takes to deploy SQL Azure from the Azure portal, and then closing with a demo where the deployment itself only took a few minutes. Hope to see you back in the other videos, and have a great day for now.