This is a part of a series “Stairway to being an Azure SQL DBA“, in which I am planning to cover everything related to working as an Azure SQL DBA.
Till now we have seen the differences between different SQL Server offerings in Azure and now we know that Azure SQL Database is the lightest one in terms of maintenance required from our end.
Once you have decided to go with the Azure SQL Database, based upon the usage and capacity estimation that you have made, the next step is to deploy the actual resource.
Deploying Azure SQL Database
An Azure SQL Database is created inside the SQL Server resource, so before you can create the database you need to deploy the SQL Server resource.
If this is the first Azure SQL Database in your environment you are given the option to create a SQL Server from Azure SQL Database resource deployment configuration page itself.
For creating SQL Server resources refer the Elastic Pool implementation blog.
Once you have built your SQL Server you can create your Azure SQL Database.
As you can see in the above pic (in Step 1) we have to provide the database name, Server and to choose whether we will be using the Elastic Pool or a single database and so have to provide the “Compute + storage” in the basic tab itself.
I have chosen to create a Basic database which has 5 DTUs.
In the next tab which is Networking, you need to select the “Private Endpoints” to provide access to the Azure SQL Database without whitelisting the IP or service in the Firewalls.
We’ll discuss this point in some other blog, for now leave everything as it is and click Additional Settings.
In the additional settings you see the below options, they are kind of self explanatory.
For the data source you can either have an empty database (choose none), use a backup (choose backup and you will be provided the option to use any backup, this backup can be from any region), or have AdventureWorks (choose Sample).
Collation is also decided at this time only, you cannot change it later. There are ways of doing this but nothing straight forward.
Now the last and most important option is left, which is also the most neglected one and that is Tags.
You should assign the appropriate Tags (it is a Name and Value combination, more onto it in later blogs). The benefit being, once you have set the proper Tags for every resource you can search them and manage them together.
Now click on “Review + Create”, the last page you will give you the summary of all the settings that you have chosen. After reviewing everything click “Create”.
You can see it checked for the SQL Server and created the database.
In later blogs we’ll see how to connect to this Database.