Learn how to create a SQL database using the Azure Resource Manager (ARM) portal and the various options available.
- Now that we understand some of the basics of CQL databases, let's go ahead and actually create and configure a CQL database in Azure. I've currently logged into Azure and am looking at my current resource groups. I already have a resource group called Implement Azure CQL Databases. I'm going to go ahead and select that. And you'll notice that I have a Lynda CQL server, I have a CQL demo, CQL database, and then I also have CQL backups, which is a recovery services vault, and we'll talk about that a little bit later.
I'm going to go ahead and create a CQL database. I'm going to click add, I'm going to start typing CQL, and I'm going to choose CQL database. Before I do so, you'll notice that I have a CQL elastic database pool. Again, this is a great solution for providers who are hosting several different databases. They can group all these databases together, to share the resources of a single pool. I'm going to choose the CQL database, and then CQL database again.
Microsoft provides a little bit of a blurb about our CQL databases, and then click create. I'm going to go ahead and enter a database name. We are creating this in the existing resource group. If I wanted to go ahead and put this in a new resource group I could have clicked create new. Next, I'm going to choose my source. We have a blank database, which will be a new, blank database. We have the very popular AdventureWorks demo database, and then we have a backup database. This will create a new database from an existing backup.
I'm going to go ahead and use a blank database. Now I'm going to go ahead and select a server. I already had the Lynda CQL server already created. I can go ahead and leverage that server again, or I can go ahead and create a new server. Please don't think that you're building a new VM here. This is just a virtual server. You're just leveraging an existing server that happens to be sitting in Azure. I'm going to go ahead and provide a server name. I'm going to keep this the same as the database name for our demonstration purposes.
You'll notice here that I have an exclamation mark, and that is because this name is already taken. I need to come up with a unique name. I'm going to go ahead and add my initials to the end, keeping my fingers crossed that that works. Yes it does. You're going to provide a server admin login and password, the location, and then do I want to use the latest v12 server. I'm going to go ahead and say yes. You will notice I cannot uncheck allow Azure services to access this server.
Don't freak out about this. This can be changed after the database has been provisioned. Click select. If I wanted to use a CQL elastic pool I would go ahead and click yes, and then configure the pool. I'm going to go ahead and click plus. I would go ahead and enter the name. I would choose my pricing tier. I'm going to go with the standard tier. And you'll notice that we have all the details about what we can do within that tier clearly listed for us, including the cost as well.
In my case this will be in Canadian dollars. Yours may look a little different depending on where you are. Click select. I'm going to go ahead and configure my pool. Again, I'm just going to leave the defaults here. I have a maximum eDTU of 100, and my minimum is zero, and then I could adjust these as necessary, and you'll notice as I add more resources, my price changes. I'm going to go ahead and close this. I'm actually not going to go ahead and create this pool.
I just wanted to show it to you for demonstration purposes. I'm going to go ahead and close this again and again. I'm going to close the feedback blade as well, and then click no. Next, I'm going to choose my pricing tier. Again, this will be very similar to what we saw in the elastic tier. And here I can see, I'm going to look at, let's say, an S1, I have 20 DTUs, I can have a database that's up to 250 GB, I can configure geo-replication, I have point in time restore, and I know this will be 35 days because this is in the standard tier, and auditing is available.
If I just scroll down to the basic tier, you'll notice the difference here. A point in time restore, we'll notice, is only seven days. And you'll notice our database can max out at 2 GB. When we move into that premium tier, we can have very robust databases. For demonstration purposes, I'm going to keep it to an S1, and then click select. I'm going to leave the collation as a default. Again you can change this as necessary, and then click create.
Your CQL database will take about 3-5 minutes or so to fully provision, and that's all there is to it. Creating a CQL database in Azure is dead simple. You saw me do it in about 2.5 minutes. In our next video, we'll go ahead and show you the provision database and then configure some of the options.
- Implementing storage blobs and Azure files
- Managing access
- Configuring diagnostics, monitoring, and analytics
- Enabling and viewing logs
- Implementing Azure SQL databases
- Implementing recovery services
- Creating an Azure Backup vault
- Configuring the Azure Backup agent
- Backing up and restoring files
- Backing up an Azure virtual machine