| title | description | services | ms.service | ms.subservice | ms.custom | ms.devlang | ms.topic | author | ms.author | ms.reviewer | ms.date |
|---|---|---|---|---|---|---|---|---|---|---|---|
DTU resource limits single databases |
This page describes some common DTU resource limits for single databases in Azure SQL Database. |
sql-database |
sql-database |
single-database |
references_regions, seo-lt-2019, sqldbrb=1 |
reference |
stevestein |
sstein |
04/09/2021 |
[!INCLUDEappliesto-sqldb]
This article provides the detailed resource limits for Azure SQL Database single databases using the DTU purchasing model.
- For DTU purchasing model limits for single databases on a server, see Overview of resource limits on a server.
- For DTU purchasing model resource limits for Azure SQL Database, see DTU resource limits single databases and DTU resource limits elastic pools.
- For vCore resource limits, see vCore resource limits - Azure SQL Database and vCore resource limits - elastic pools.
- For more information regarding the different purchasing models, see Purchasing models and service tiers.
Each read-only replica has its own resources such as DTUs, workers, and sessions. Each read-only replica is subject to the resource limits detailed later in this article.
The following tables show the resources available for a single database at each service tier and compute size. You can set the service tier, compute size, and storage amount for a single database using:
Important
For scaling guidance and considerations, see Scale a single database
| Compute size | Basic |
|---|---|
| Max DTUs | 5 |
| Included storage (GB) | 2 |
| Max storage (GB) | 2 |
| Max in-memory OLTP storage (GB) | N/A |
| Max concurrent workers (requests) | 30 |
| Max concurrent sessions | 300 |
Important
The Basic service tier provides less than one vCore (CPU). For CPU-intensive workloads, a service tier of S3 or greater is recommended.
Regarding data storage, the Basic service tier is placed on Standard Page Blobs. Standard Page Blobs use hard disk drive (HDD)-based storage media and are best suited for development, testing, and other infrequently accessed workloads that are less sensitive to performance variability.
| Compute size | S0 | S1 | S2 | S3 |
|---|---|---|---|---|
| Max DTUs | 10 | 20 | 50 | 100 |
| Included storage (GB) 1 | 250 | 250 | 250 | 250 |
| Max storage (GB) | 250 | 250 | 250 | 1024 |
| Max in-memory OLTP storage (GB) | N/A | N/A | N/A | N/A |
| Max concurrent workers (requests) | 60 | 90 | 120 | 200 |
| Max concurrent sessions | 600 | 900 | 1200 | 2400 |
1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.
Important
The Standard S0, S1 and S2 tiers provide less than one vCore (CPU). For CPU-intensive workloads, a service tier of S3 or greater is recommended.
Regarding data storage, the Standard S0 and S1 service tiers are placed on Standard Page Blobs. Standard Page Blobs use hard disk drive (HDD)-based storage media and are best suited for development, testing, and other infrequently accessed workloads that are less sensitive to performance variability.
| Compute size | S4 | S6 | S7 | S9 | S12 |
|---|---|---|---|---|---|
| Max DTUs | 200 | 400 | 800 | 1600 | 3000 |
| Included storage (GB) 1 | 250 | 250 | 250 | 250 | 250 |
| Max storage (GB) | 1024 | 1024 | 1024 | 1024 | 1024 |
| Max in-memory OLTP storage (GB) | N/A | N/A | N/A | N/A | N/A |
| Max concurrent workers (requests) | 400 | 800 | 1600 | 3200 | 6000 |
| Max concurrent sessions | 4800 | 9600 | 19200 | 30000 | 30000 |
1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.
| Compute size | P1 | P2 | P4 | P6 | P11 | P15 |
|---|---|---|---|---|---|---|
| Max DTUs | 125 | 250 | 500 | 1000 | 1750 | 4000 |
| Included storage (GB) 1 | 500 | 500 | 500 | 500 | 4096 2 | 4096 2 |
| Max storage (GB) | 1024 | 1024 | 1024 | 1024 | 4096 2 | 4096 2 |
| Max in-memory OLTP storage (GB) | 1 | 2 | 4 | 8 | 14 | 32 |
| Max concurrent workers (requests) | 200 | 400 | 800 | 1600 | 2800 | 6400 |
| Max concurrent sessions | 30000 | 30000 | 30000 | 30000 | 30000 | 30000 |
1 See SQL Database pricing options for details on additional cost incurred due to any extra storage provisioned.
2 From 1024 GB up to 4096 GB in increments of 256 GB.
Important
More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, and Germany Northeast. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see P11-P15 current limitations.
[!NOTE]
For tempdb limits, see tempdb limits.
- For vCore resource limits for a single database, see resource limits for single databases using the vCore purchasing model
- For vCore resource limits for elastic pools, see resource limits for elastic pools using the vCore purchasing model
- For DTU resource limits for elastic pools, see resource limits for elastic pools using the DTU purchasing model
- For resource limits for managed instances in Azure SQL Managed Instance, see SQL Managed Instance resource limits.
- For information about general Azure limits, see Azure subscription and service limits, quotas, and constraints.
- For information about resource limits on a logical SQL server, see overview of resource limits on a logical SQL server for information about limits at the server and subscription levels.