In the First part of this series we talked about the concept of Azure SQL services (PAAS) and how this service provide a very useful and easy way for SQL administrators to build their databases in cloud.
Also we explained in the first part the difference between SQL as Infrastructure AS A Service and SQL as Platform As A service, we explained also some scenarios which will help the SQL admins to decide which type of SQL to use IAAS or PAAS.
Now, let’s show you some technical steps how to create an Azure SQL service and what is the available options for implementing this service.
As usual, you should login to Azure portal using your account https://manage.windowsazure.com, then go to SQL DATABASES tab:
Then click in the New Button in the bottom of the page:
Choose Data services -> SQL DATABASE -> Custom Create:
Now fill the required information:
Name: The name of the SQL database.
Subscription: if you have more than one azure subscription, choose the one you want to use.
Service Tiers: choose the type of database you need to use, each type have it’s own cost ( later in this article we will discuss the tiers).
Performance Level: choose the DTU’s performance you need (later in this article we will discuss the tiers).
Collation: choose the appropriate collation type that match your requirements.
Server: since you don’t have any server before, choose New SQL Server option to create new server, if you have an server already you can deploy more than one database in same server.
Now, New Wizard option will be displayed since you chose the creation of new server, fill the login credential.
In Azure SQL Service (PAAS), you don’t have the option of windows authentication to SQL, you can use only SQL authentication method
Now in the database tab you will see that the process of the DATABASE starting:
if you switch to servers tab; also new server in the creation process, note that the name of server will be automatically generated:
After minutes, the database and server is ready for use:
Azure SQL service Tier:
As we noticed in the creation wizard of the SQL database we need to choose the SQL service tier option to be Basic, Standard or Premium, so let’s talk a little bit about the difference between these three options.
Basic Tier is recommended for small size databases, it support only one active operation at the time, it’s useful for testing environment, the max size of this database is 2 GB.
Standard Tier is the common used in most of customers, it supported multiple queries at the time, the max size of this database is 250 GB.
Premium Tier supporting a large number of concurrent users and requiring the highest level of business continuity capabilities, for examples databases supporting mission critical applications, the max size of this database is 500 GB or 1 TB for specific Type.
Below table summarize the difference between the service tier options:
In above table there is an option talked about the number of DTU’s supported by each tier, so what is this option mean, I found a simple way in one article that describe the meaning of DTU’s:
Database throughput Unit (DTUs) provide a way to describe the relative capacity of a performance level of Basic, Standard, and Premium databases. DTUs are based on a blended measure of CPU, memory, reads, and writes. As DTUs increase, the power offered by the performance level increases. For example, a performance level with 5 DTUs has five times more power than a performance level with 1 DTU. A maximum DTU quota applies to each server.
Finally, for price calculation you can use Azure calculator at :
In next part, we will show you some configuration of the Azure SQL Services and hos to connect to the database and create some tables using a real example.
About Blogger …
Ahmad Yasin in a Microsoft Cloud Engineer and the publisher of
AzureDummies blog. He also hold many certificates in office 365
and windows azure including Developing Microsoft Azure Solutions, Implementing Microsoft Azure Infrastructure Solutions
and MCSA office 365.