Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Professional Azure SQL Database Administration

You're reading from   Professional Azure SQL Database Administration Equip yourself with the skills to manage and maintain data in the cloud

Arrow left icon
Product type Paperback
Published in Jul 2019
Publisher Packt
ISBN-13 9781789802542
Length 562 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Ahmad Osama Ahmad Osama
Author Profile Icon Ahmad Osama
Ahmad Osama
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

About the Book 1. Microsoft Azure SQL Database Primer FREE CHAPTER 2. Migrating a SQL Server Database to an Azure SQL Database 3. Backing Up an Azure SQL Database 4. Restoring an Azure SQL Database 5. Securing an Azure SQL Database 6. Scaling out an Azure SQL Database 7. Azure SQL Database Elastic Pools 8. High Availability and Disaster Recovery 9. Monitoring and Tuning Azure SQL Database 10. Database Features

Introducing Elastic Pools

Azure SQL Database Elastic Pool is a cost-effective solution for managing and scaling a group or a pool of Azure SQL databases, with a utilization pattern characterized by low average utilization and infrequent spikes.

Figure 7.1: Elastic pools

All databases in an elastic pool:

  • Belong to one Azure SQL server
  • Share a set number of eDTUs
  • Share a set amount of elastic pool storage
  • Are priced for eDTUs and not individual databases like DTUs
  • Can scale up to the given maximum amount of eDTUs
  • Have a guaranteed minimum number of eDTUs

When Should You Consider Elastic Pools?

In Lesson 6, Scaling Out an Azure SQL Database, we worked on sharding the toystore database into four individual shards. Each shard had 50 pieces of a customer's/tenant's data. Let's say that each individual database is sized to a Standard S3 service tier, for example, 100 DTUs, and has the DTU utilization levels shown in the following graph:

...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime