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
Copy file name to clipboardExpand all lines: azure-sql/database/elastic-pool-scale.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,17 +45,15 @@ Changing the service tier or compute size of an elastic pool follows a similar p
45
45
46
46
The estimated latency to change the service tier, scale the compute size of a single database or elastic pool, move a database in/out of an elastic pool, or move a database between elastic pools is parameterized as follows:
47
47
48
-
|Service tier|Basic single database,</br>Standard (S0-S1)|Basic elastic pool,</br>Standard (S2-S12), </br>General Purpose single database or elastic pool|Premium or Business Critical single database or elastic pool|Hyperscale
49
-
|:---|:---|:---|:---|:---|
50
-
|**Basic single database,</br> Standard (S0-S1)**|• Constant time latency independent of space used</br>• Typically, less than 5 minutes|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|
51
-
|**Basic elastic pool, </br>Standard (S2-S12), </br>General Purpose single database or elastic pool**|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• For single databases, constant time latency independent of space used</br>• Typically, less than 5 minutes for single databases</br>• For elastic pools, proportional to the number of databases|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|
52
-
|**Premium or Business Critical single database or elastic pool**|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|
53
-
|**Hyperscale**|N/A|N/A|N/A|• Constant time latency independent of space used</br>• Typically, less than 2 minutes|
48
+
| Elastic pool scaling latency | To Basic, Standard, General Purpose elastic pool | To Premium, Business Critical elastic pool | To Hyperscale elastic pool |
49
+
|:-|:-|:-|:-|
50
+
|**From Basic, Standard, General Purpose elastic pool**| Proportional to the number of databases |• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used | N/A – databases need to be added individually to [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md#limitations). Scaling latency per database documented in [Scale single database resources](single-database-scale.md)|
51
+
|**From Premium, Business Critical elastic pool**|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used |• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used | N/A – databases need to be added individually to [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md#limitations). Scaling latency per database documented in [Scale single database resources](single-database-scale.md)|
52
+
|**From Hyperscale elastic pool**| N/A | N/A |• Constant time latency independent of space used</br>• Typically, less than 2 minutes |
54
53
55
54
> [!NOTE]
56
55
>
57
-
> - In the case of changing the service tier or scaling compute for an elastic pool, the summation of space used across all databases in the pool should be used to calculate the estimate.
58
-
> - In the case of moving a database to/from an elastic pool, only the space used by the database impacts the latency, not the space used by the elastic pool.
56
+
> - When changing the service tier or scaling compute for any non-Hyperscale elastic pool, the summation of space used across all databases in the pool should be used to calculate the estimate. Scaling latency for Hyperscale elastic pools is independent of space used.
59
57
> - For Standard and General Purpose elastic pools, latency of moving a database in/out of an elastic pool or between elastic pools will be proportional to database size if the elastic pool is using Premium File Share ([PFS](/azure/storage/files/storage-files-introduction)) storage. To determine if a pool is using PFS storage, execute the following query in the context of any database in the pool. If the value in the AccountType column is `PremiumFileStorage` or `PremiumFileStorage-ZRS`, the pool is using PFS storage.
60
58
61
59
```sql
@@ -67,6 +65,12 @@ FROM sys.database_files AS s
67
65
WHEREs.type_descIN ('ROWS', 'LOG');
68
66
```
69
67
68
+
> [!NOTE]
69
+
> - The zone redundant property will remain the same by default when scaling an elastic pool from the Business Critical to the General Purpose tier.
70
+
> - Latency for the scaling operation when zone redundancy is changed for a General Purpose elastic pool is proportional to database size.
71
+
> - Changing an existing non-Hyperscale elastic pool to the Hyperscale edition isn't supported. See [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md#limitations) for more details. Instead, databases need to be added individually to Hyperscale elastic pools.
72
+
> - Changing the edition of a Hyperscale elastic pool to a non-Hyperscale edition isn't supported. See [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md#limitations) for more details.
73
+
70
74
> [!TIP]
71
75
> To monitor in-progress operations, see: [Manage operations using the SQL REST API](/rest/api/sql/operations/list), [Manage operations using CLI](/cli/azure/sql/db/op), [Monitor operations using T-SQL](/sql/relational-databases/system-dynamic-management-views/sys-dm-operation-status-azure-sql-database) and these two PowerShell commands: [Get-AzSqlDatabaseActivity](/powershell/module/az.sql/get-azsqldatabaseactivity) and [Stop-AzSqlDatabaseActivity](/powershell/module/az.sql/stop-azsqldatabaseactivity).
Copy file name to clipboardExpand all lines: azure-sql/database/hyperscale-elastic-pool-overview.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ For greater detail, see the [Hyperscale elastic pool resource limits](resource-l
86
86
87
87
## Limitations
88
88
89
-
During preview, consider the following limitations:
89
+
Consider the following limitations:
90
90
91
91
- Changing an existing non-Hyperscale elastic pool to the Hyperscale edition isn't supported. Individual databases need to be moved out of their respective existing pool before they can be added to the Hyperscale elastic pool.
92
92
- Changing the edition of a Hyperscale elastic pool to a non-Hyperscale edition isn't supported.
Copy file name to clipboardExpand all lines: azure-sql/database/single-database-scale.md
+11-10Lines changed: 11 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,17 +44,17 @@ Changing the service tier or compute size of mainly involves the service perform
44
44
45
45
The estimated latency to change the service tier, scale the compute size of a single database or elastic pool, move a database in/out of an elastic pool, or move a database between elastic pools is parameterized as follows:
46
46
47
-
|Service tier|Basic single database,</br>Standard (S0-S1)|Basic elastic pool,</br>Standard (S2-S12),</br>General Purpose single database or elastic pool|Premium or Business Critical single database or elastic pool|Hyperscale
48
-
|:---|:---|:---|:---|:---|
49
-
|**Basic single database,</br>Standard (S0-S1)**|• Constant time latency independent of space used</br>• Typically, less than 5 minutes|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|
50
-
|**Basic elastic pool, </br>Standard (S2-S12),</br>General Purpose single database or elastic pool**|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• For single databases, constant time latency independent of space used</br>• Typically, less than 5 minutes for single databases</br>• For elastic pools, proportional to the number of databases|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|
51
-
|**Premium or Business Critical single database or elastic pool**|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|
52
-
|**Hyperscale**|N/A|See [Reverse migrate from Hyperscale](manage-hyperscale-database.md#reverse-migrate-from-hyperscale)|N/A|• Constant time latency independent of space used</br>• Typically, less than 2 minutes|
47
+
| Database scaling latency | To Basic single database,</br>Standard single database (S0-S1)| To Standard single database (S2-S12),</br>General Purpose single database,</br>Basic elastic pooled database,</br>Standard elastic pooled database,</br>General Purpose pooled database | To Premium single database or pooled database,</br>Business Critical single database or pooled database | To Hyperscale single database or pooled database |
48
+
|:-|:-|:-|:-|:-|
49
+
|**From Basic single database,</br>Standard single database (S0-S1)**|• Constant time latency independent of space used</br>• Typically, less than 5 minutes|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|
50
+
|**From Basic pooled database,</br>Standard single database (S2-S12),</br>Standard pooled database,</br>General Purpose single database or pooled database**|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• For single databases, constant time latency independent of space used</br>• Typically, less than 5 minutes for single databases</br>• For elastic pools, proportional to the number of databases|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|
51
+
|**From Premium single database or pooled database,</br>Business Critical single database or pooled database**|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|• Latency proportional to database space used due to data copying</br>• Typically, less than 1 minute per GB of space used|
52
+
|**From Hyperscale single database or pooled database**|N/A|See [Reverse migrate from Hyperscale](manage-hyperscale-database.md#reverse-migrate-from-hyperscale) for supported scenarios and limitations. |N/A|• Constant time latency independent of space used</br>• Typically, less than 2 minutes|
53
53
54
54
> [!NOTE]
55
-
> Additionally, for Standard (S2-S12) and General Purpose databases, latency for moving a database in/out of an elastic pool or between elastic pools will be proportional to database size if the database is using Premium File Share ([PFS](/azure/storage/files/storage-files-introduction)) storage.
56
-
>
57
-
> To determine if a database is using PFS storage, execute the following query in the context of the database. If the value in the AccountType column is `PremiumFileStorage` or `PremiumFileStorage-ZRS`, the database is using PFS storage.
55
+
> -Additionally, for Standard (S2-S12) and General Purpose databases, latency for moving a database in/out of an elastic pool or between elastic pools will be proportional to database size if the database is using Premium File Share ([PFS](/azure/storage/files/storage-files-introduction)) storage.
56
+
>- In the case of moving a database to/from an elastic pool, only the space used by the database impacts the latency, not the space used by the elastic pool.
57
+
> -To determine if a database is using PFS storage, execute the following query in the context of the database. If the value in the AccountType column is `PremiumFileStorage` or `PremiumFileStorage-ZRS`, the database is using PFS storage.
58
58
59
59
```sql
60
60
SELECTs.file_id,
@@ -66,7 +66,8 @@ WHERE s.type_desc IN ('ROWS', 'LOG');
66
66
```
67
67
68
68
> [!NOTE]
69
-
> The zone redundant property will remain the same by default when scaling from the Business Critical to the General Purpose tier. Latency for this downgrade when zone redundancy is enabled as well as latency for switching to zone redundancy for the General Purpose tier will be proportional to database size.
69
+
> - The zone redundant property will remain the same by default when scaling a single database from the Business Critical to the General Purpose tier.
70
+
> - Latency for the scaling operation when zone redundancy is changed for a General Purpose single database is proportional to database size.
70
71
71
72
> [!TIP]
72
73
> To monitor in-progress operations, see: [Manage operations using the SQL REST API](/rest/api/sql/operations/list), [Manage operations using CLI](/cli/azure/sql/db/op), [Monitor operations using T-SQL](/sql/relational-databases/system-dynamic-management-views/sys-dm-operation-status-azure-sql-database) and these two PowerShell commands: [Get-AzSqlDatabaseActivity](/powershell/module/az.sql/get-azsqldatabaseactivity) and [Stop-AzSqlDatabaseActivity](/powershell/module/az.sql/stop-azsqldatabaseactivity).
0 commit comments