You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|IO latency (approximate)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|
@@ -60,7 +59,6 @@ You can set the service tier, compute size, and storage amount using the [Azure
60
59
61
60
\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and its max vCore per database is 2, then the max concurrent workers is 200. If max vCore per database is 0.5, then the max concurrent workers is 50 since on Gen5 there are a max of 100 concurrent workers per vcore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
62
61
63
-
64
62
### General purpose service tier: Generation 4 compute platform (part 2)
|IO latency (approximate)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|
@@ -89,7 +87,6 @@ You can set the service tier, compute size, and storage amount using the [Azure
89
87
90
88
\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and its max vCore per database is 2, then the max concurrent workers is 200. If max vCore per database is 0.5, then the max concurrent workers is 50 since on Gen5 there are a max of 100 concurrent workers per vcore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
91
89
92
-
93
90
## General purpose - provisioned compute - Gen5
94
91
95
92
### General purpose service tier: Generation 5 compute platform (part 1)
@@ -102,8 +99,8 @@ You can set the service tier, compute size, and storage amount using the [Azure
102
99
|Max number DBs per pool|100|200|500|500|500|500|500|
|IO latency (approximate)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|
@@ -130,8 +127,8 @@ You can set the service tier, compute size, and storage amount using the [Azure
130
127
|Max number DBs per pool|500|500|500|500|500|500|500|
|IO latency (approximate)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|5-7 ms (write)<br>5-10 ms (read)|
@@ -172,42 +169,38 @@ You can set the service tier, compute size, and storage amount using the [Azure
172
169
|Read Scale-out|N/A|
173
170
|Included backup storage|1X DB size|
174
171
175
-
176
-
177
-
178
172
\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and its max vCore per database is 2, then the max concurrent workers is 200. If max vCore per database is 0.5, then the max concurrent workers is 50 since on Gen5 there are a max of 100 concurrent workers per vcore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
179
173
180
-
181
174
## Business critical - provisioned compute - Gen4
182
175
183
176
> [!IMPORTANT]
184
177
> New Gen4 databases are no longer supported in the Australia East or Brazil South regions.
185
178
186
179
### Business critical service tier: Generation 4 compute platform (part 1)
|IO latency (approximate)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|
|IO latency (approximate)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|
|Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
211
204
212
205
\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and its max vCore per database is 2, then the max concurrent workers is 200. If max vCore per database is 0.5, then the max concurrent workers is 50 since on Gen5 there are a max of 100 concurrent workers per vcore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
213
206
@@ -222,8 +215,8 @@ You can set the service tier, compute size, and storage amount using the [Azure
|Max data size (GB)|1024|1024|1024|1024|1024|1024|
219
+
|Max log size (GB)|307|307|307|307|307|307|
227
220
|TempDB size (GB)|224|256|288|320|384|384|
228
221
|IO latency (approximate)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|
|IO latency (approximate)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|
|IO latency (approximate)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|1-2 ms (write)<br>1-2 ms (read)|
|Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
260
+
|Read Scale-out|Yes|Yes|Yes|Yes|Yes|Yes|
261
+
|Included backup storage|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|1X DB size|
269
262
270
263
\* For the max concurrent workers (requests) for any individual database, see [Single database resource limits](sql-database-vcore-resource-limits-single-databases.md). For example, if the elastic pool is using Gen5 and its max vCore per database is 2, then the max concurrent workers is 200. If max vCore per database is 0.5, then the max concurrent workers is 50 since on Gen5 there are a max of 100 concurrent workers per vcore. For other max vCore settings per database that are less 1 vCore or less, the number of max concurrent workers is similarly rescaled.
0 commit comments