Elastic Pools: How to implement it?

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.

Once you know what it is an Elastic Pool and have decided to implement it, the first thing to create is a SQL Server resource, which is the logical container of all the Azure SQL Databases and Elastic Pools too.

To create SQL Server you just need a Server name, location, and an Admin along with the password. The name of the server should be unique globally in the whole Azure environment and also the location best practice is to have it closer to your Application. As previously stated it is just a logical container the databases inside this SQL Server could be in any location but still preferred to be near your application location.

Creating SQL Server

Basic SQL Server setting

The next option is to set the Firewall for this SQL Server for allowing different Azure services to access this server, it is as easy setting radio button to Yes or No.

Network for SQL Server

The other options can be set as default.

Creating Elastic Pool

Elastic Pool can be created from either inside the SQL Server resource or search for Elastic Pool and create from there. Both the methods of creating Elastic Pool is same once in, it’s just the two different paths of doing the same thing.

Once in, you are given the option to choose an Elastic Pool Name, the server for which you are creating this Pool and the configuration (size of the pool).

Creating Elastic Pool

In the configure part of the Elastic Pool we just don’t have the option to set the resource pool but also adding databases into this pool and we can also set the max DTU a single database can use.

Adding Databases 1

When you click on “+ Add databases” you are given the option to choose the databases in the SQL Server where we are creating our Elastic Pool.

Per Database Settings

The per database setting for an Elastic Pool is allocating the maximum DTU possible for each database inside the pool. The use of it is to make sure that one rogue database doesn’t runaway will all the resources of the pool.

Per database settings

Once everything is done click Apply for the configuration and click “Review + Create” for the Elastic Pool.

Adding database into an Elastic Pool

If you have an existing Elastic Pool and want to add a new database into it, the database should be in the same SQL Server where your Elastic Pool is (the databases can also be moved from one server to another we’ll discuss it later blogs).

When creating the Azure SQL Database you can choose to use an Elastic Pool and provide the Elastic Pool name.

If you have an existing database and also an Elastic pool, go to your Elastic Pool and choose the Configure under Settings. Go to the Databases tab and select “+ Add databases”.

Choose the database to add and click Apply and you are done.

That is all for creating an Elastic Pool and adding databases into it, in the next blog we’ll see how to identify which all databases can be grouped together into an Elastic Pool.

One thought on “Elastic Pools: How to implement it?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s