Skip to content

Commit c0467a2

Browse files
alexbuckgitMashaMSFTdenreav-aljeWilliamDAssafMSFT
authored
[DO NOT MERGE] Integration branch for Build 2023 (#27146)
* fixing toc * 20230411 ctas * 20230411 data types * 20230411 collations * 20230411 insert * 20230411 2057 data type synonyms * 20230412 varbinary * 20230412 date and time * 20230412 1358 * 20230412 statistics * Adding the article version for Fabric * 20230412 Kevin Conan - Create Table - removed binary data type * Correcting errors to address Acrolinx report * Correction to !include references * 20230412 Kevin Conan - Create Table - removed binary data type 2 * 20230412 1510 statistics * 20230412 1521 * 20230412 metadata, notes * 20230412 update stats * Update copy-into-transact-sql.md * Update copy-into-transact-sql.md * Update copy-into-transact-sql.md * 20230412 dm tran locks * 20230412 copy into * Apply suggestions from code review Acrolinx fixes * Updates to reflect stakeholder feedback * Addressing Acrolinx feedback * Adding fabric moniker page for CTAS * Addressing Acrolinx feedback * Minor corrections * 20230414 collation * 20230414 1124 * 20230414 fabric syntax * 20230417 1136 * 20230417 1140 * 20230417 1153 * 20230417 1157 * 20230417 1215 * 20230417 fabric * 20230417 fabric * 20230420 ctas, applicability for fabric * 20230420 fabric include, link * 20230421 revert Lakehouse SQL Endpoint, apply fabric to objectproperty * 20230424 fix links for SE and DW article refactor * 20230424 alter table column constraint * 20230424 moniker * Fix two typos * 20230425 1926 * 20230426 Kevin Conan - added note that precision is now required for datetime2 and time data types * Update docs/t-sql/statements/create-table-azure-sql-data-warehouse.md * Update docs/t-sql/statements/create-table-azure-sql-data-warehouse.md * 20230428 fabric tsql reference * 20230428 fabric tsql reference * 20230501 ctas/insert * 20230501 1643 * 20230503 fabric applicability * 20230503 fabric applicability * 20230503 fabric applicability * 20230503 fabric applicability * 20230503 fabric applicability * 20230503 fabric applicability * 20230503 fabric applicability * 20230503 link fix * 20230503 include link fix * 20230504 Kevin Conan - add Synapse Data Warehouse include tags for 3 transaction related items * add base64 tsql functions docs * simplify per suggestion * started writing content * staging resource limits page * defining architecture * finished overview * adding release notes * started writing content * updating toc * staging resource limits page * finished overview * Update limits for Hyperscale elastic pools * fixing toc * Address issues flagged by Acrolinx * Apply suggestions from code review * 20230505 edit pass, add links * 20230505 add base64 * 20230505 better error message * 20230505 url safe error messages * 202320508 datetrunc * 20230508 bitwise functions in fabric * 20230508 1104 update/delete fabric remark * 20230508 alter role * 20230508 fabric * 20230508 fabric applicability * Add basic actions for Hyperscale elastic pools * Add known issues section * Address Acrolinx feedback * Fix build warnings * 20230508 rework trim, ltrim, rtrim ranges * 20230508 1605 fabric * 20230508 alter role includes * 20230508 1744 fabric applicability * 20230508 fabric applicability * 20230508 fabric applicability * 20230508 fabric applicability * 20230508 sample apply for fabric * 20230508 use * 20230509 1009 fabric * edited article, added diagram * adding vCore Connection instructions * 20230509 fabric applicability * 20230509 fabric applicability * updating pr comments * 20230509 fabric syntax block * Minor edits to Limitations section * 20230509 fabric applicability * 20230509 new include * Add preview note to Limits page * updating pr comments * 20230510 fabric applicability * 20230510 fabric applicability * 20230510 fabric applicability * 20230510 fabric applicability * 20230510 fabric applicability * Update docs/azure-data-studio/quickstart-azure-cosmos-db-mongodb.md Co-authored-by: Sidney Andrews <sidandrews@microsoft.com> * Update docs/azure-data-studio/quickstart-azure-cosmos-db-mongodb.md Co-authored-by: Sidney Andrews <sidandrews@microsoft.com> * a few stylistic changes * Minor edits to the limits page * Add link to the HS elastic pools architecture section * 20230510 1230 name change to warehouse * 20230510 fabric * 20230510 fabric * Update copy-into-transact-sql.md Adding a note about date formats * Acrolinx feedback * Minor updates to the syntax. Separating better reflecting the Applies To section to Fabric and Synapse * 20230510 fabric * Adding a remark about filegroups in Fabric * Correcting build error * fixing blocking and non-blocking issues * Correction to the syntax * Update create-table-as-select-azure-sql-data-warehouse.md * 20230511 fix metadata * 20230511 fix metadata * 20230515 remove broken link * 20230515 add fabric applicability * [BULK] DocuTune - Add ms.custom tags for Build 2023 content --------- Co-authored-by: Masha Thomas <32783170+MashaMSFT@users.noreply.github.com> Co-authored-by: Dennis Rea <v-denrea@microsoft.com> Co-authored-by: Alma Jenks <v-alje@microsoft.com> Co-authored-by: WilliamDAssafMSFT <wiassaf@microsoft.com> Co-authored-by: Stacyrch140 <102548089+Stacyrch140@users.noreply.github.com> Co-authored-by: Pericles (Peri) Rocha <procha@microsoft.com> Co-authored-by: Kevin Conan <56314801+KevinConanMSFT@users.noreply.github.com> Co-authored-by: Anna Huff <92125952+AnnaMHuff@users.noreply.github.com> Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com> Co-authored-by: Jill Grant <v-jillg@microsoft.com> Co-authored-by: Regan Downer <v-rdowner@microsoft.com> Co-authored-by: Colin Cooper <72402153+v-ccolin@users.noreply.github.com> Co-authored-by: Jeff Borsecnik <123032460+American-Dipper@users.noreply.github.com> Co-authored-by: Aaron Pitman <aaronpitman@microsoft.com> Co-authored-by: Arvind Shyamsundar <arvindsh@microsoft.com> Co-authored-by: Shilpa Sharma <v-shils@microsoft.com> Co-authored-by: Estefani Arroyo <29219340+StefArroyo@users.noreply.github.com> Co-authored-by: Sidney Andrews <sidandrews@microsoft.com> Co-authored-by: James Barnett <v-jabarnett@microsoft.com> Co-authored-by: Mike Ray (SQL) <mikeray@microsoft.com> Co-authored-by: Tracey Torble <v-trtorb@microsoft.com> Co-authored-by: Cory Fowler <441607+SyntaxC4@users.noreply.github.com>
1 parent da2e6e5 commit c0467a2

File tree

487 files changed

+3445
-1387
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

487 files changed

+3445
-1387
lines changed

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

+6-2
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn about the new features and documentation improvements for Azu
55
author: WilliamDAssafMSFT
66
ms.author: wiassaf
77
ms.reviewer: mathoma
8-
ms.date: 05/03/2023
8+
ms.date: 05/21/2023
99
ms.service: sql-database
1010
ms.subservice: service-overview
1111
ms.topic: conceptual
@@ -39,6 +39,7 @@ The following table lists the features of Azure SQL Database that are currently
3939
| [Elastic jobs](elastic-jobs-overview.md) | The elastic jobs feature is the SQL Server Agent replacement for Azure SQL Database as a PaaS offering. |
4040
| [Elastic queries](elastic-query-overview.md) | The elastic queries feature allows for cross-database queries in Azure SQL Database. |
4141
| [Elastic transactions](elastic-transactions-overview.md) | Elastic transactions allow you to execute transactions distributed among cloud databases in Azure SQL Database. |
42+
| [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md) | Manage and scale multiple Hyperscale databases in Azure SQL Database by using Hyperscale elastic pools. |
4243
| [Hyperscale long-term retention](long-term-retention-overview.md) | Save your Hyperscale database backups for up to 10 years with long-term retention (LTR). |
4344
| [Hyperscale RA-GZRS](hyperscale-automated-backups-overview.md#data-and-backup-storage-redundancy) | Store your Hyperscale database backups on read access geo-zone-redundancy (RA-GZRS) storage. |
4445
| [Hyperscale premium-series and premium-series memory optimized hardware](service-tier-hyperscale.md#compute-resources) | Premium-series and premium-series memory optimized hardware is now available for Hyperscale databases.|
@@ -86,13 +87,16 @@ The following table lists the new generally available (GA) features of Azure SQL
8687

8788
Learn about significant changes to the Azure SQL Database documentation. For previous years, see the [What's new archive](doc-changes-updates-release-notes-whats-new-archive.md).
8889

90+
8991
### May 2023
9092

9193
| Changes | Details |
9294
| --- | --- |
9395
| **Cross-tenant CMK with TDE GA** | Cross-tenant CMK with TDE allows SQL databases to be in a separate tenant than the tenant holding the Azure Key Vault resource used to encrypt the databases. This feature is now generally available. To learn more, review [Cross-tenant CMK with TDE](transparent-data-encryption-byok-cross-tenant.md). |
96+
| **Hyperscale elastic pools preview**| Manage and scale multiple Hyperscale databases in Azure SQL Database by using Hyperscale elastic pools. This feature is now in preview. See [Hyperscale elastic pools](hyperscale-elastic-pool-overview.md) to learn more. |
9497
| **Optimized locking available in Hyperscale** | Optimized locking is a new Database Engine capability that offers an improved locking mechanism that reduces lock memory consumption and blocking amongst concurrent transactions. This fundamentally improves concurrency and lowers lock memory. Optimized locking is now available in all DTU and vCore service tiers, including provisioned and serverless. For more information, see [Optimized locking](/sql/relational-databases/performance/optimized-locking). |
9598

99+
96100
### April 2023
97101

98102
| Changes | Details |
@@ -105,7 +109,7 @@ Learn about significant changes to the Azure SQL Database documentation. For pre
105109
| --- | --- |
106110
| **Approximate Percentile GA** | Quickly compute percentiles for a large dataset with acceptable rank-based error bounds to help make rapid decisions by using approximate percentile aggregate. This feature is generally available now. Review [Approximate percentile](/sql/t-sql/functions/approx-percentile-cont-transact-sql) to learn more. |
107111
| **Shrink Database / Shrink File with Low Priority GA** | This feature solves the concurrency issues that can arise from shrink database and shrink file commands, especially during active maintenance or on busy OLTP environments. In WAIT_AT_LOW_PRIORITY mode, necessary tasks to shrink database files can be completed without negatively affecting application query performance. Review [Shrink Database](/sql/t-sql/database-console-commands/dbcc-shrinkdatabase-transact-sql?view=azuresqldb-current&preserve-view=true) and [Shrink File with Low Priority](/sql/t-sql/database-console-commands/dbcc-shrinkfile-transact-sql?view=azuresqldb-current&preserve-view=true). |
108-
| **Database level CMK with TDE preview** | Previously, TDE with CMK is set at the server level, and is inherited by all encrypted databases associated with that server. Database level CMK allows setting the TDE protector as a customer-managed key individually for each database within the server. This feature is currently in preview. Review [Transparent data encryption (TDE) with customer-managed keys at the database level](transparent-data-encryption-byok-database-level-overview.md) to learn more. |
112+
| **Database level CMK with TDE preview** | Previously, TDE with CMK was set at the server level, and was inherited by all encrypted databases associated with that server. Database level CMK allows setting the TDE protector as a customer-managed key individually for each database within the server. This feature is currently in preview. Review [Transparent data encryption (TDE) with customer-managed keys at the database level](transparent-data-encryption-byok-database-level-overview.md) to learn more. |
109113

110114
### February 2023
111115

azure-sql/database/elastic-pool-overview.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 06/23/2021
88
ms.service: sql-database
99
ms.subservice: elastic-pools
1010
ms.topic: conceptual
11-
ms.custom: sqldbrb=1
11+
ms.custom: sqldbrb=1, build-2023, build-2023-dataai
1212
---
1313
# Elastic pools help you manage and scale multiple databases in Azure SQL Database
1414
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]

azure-sql/database/hyperscale-architecture.md

+1
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ ms.reviewer: wiassaf, mathoma
77
ms.date: 2/17/2022
88
ms.service: sql-database
99
ms.subservice: service-overview
10+
ms.custom: build-2023, build-2023-dataai
1011
ms.topic: conceptual
1112
---
1213

Original file line numberDiff line numberDiff line change
@@ -0,0 +1,176 @@
1+
---
2+
title: Working with Hyperscale elastic pools using command-line tools
3+
description: Working with Hyperscale elastic pools using command-line tools such as the Azure CLI and PowerShell.
4+
author: arvindshmicrosoft
5+
ms.author: arvindsh
6+
ms.reviewer: wiassaf, mathoma
7+
ms.date: 05/21/2023
8+
ms.service: sql-database
9+
ms.subservice: elastic-pools
10+
ms.topic: conceptual
11+
ms.custom:
12+
---
13+
# Working with Hyperscale elastic pools using command-line tools
14+
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
15+
16+
In this article, learn to create, scale, and move databases into a [Hyperscale elastic pool](hyperscale-elastic-pool-overview.md) using command line tools such as the Azure CLI and PowerShell. In addition to these methods, you can always use the Azure portal for most operations.
17+
18+
19+
> [!NOTE]
20+
> Hyperscale elastic pools are in public preview. This preview feature is available for Azure SQL Database (Hyperscale service tier). It is not available for Azure SQL Managed Instance, SQL Server on-premises, SQL Server on Azure VMs, or Azure Synapse Analytics (dedicated SQL pools (formerly SQL DW)).
21+
22+
23+
24+
## Prerequisites
25+
26+
To work with your Hyperscale elastic pool, you should have:
27+
28+
- An Azure subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/).
29+
- A [logical server in Azure](logical-servers.md) deployed to a [resource group](/azure/azure-resource-manager/management/manage-resource-groups-portal). The examples in this article use the name `my-example-rg` for the resource group, and `my-example-sql-svr` for the logical server.
30+
- The latest version of Azure PowerShell [Az.Sql.3.11.0 or higher](https://www.powershellgallery.com/packages/Az.Sql/3.11.0) or the Azure CLI [Az version 2.40.0 or higher](/cli/azure/install-azure-cli)
31+
32+
33+
## Create a new Hyperscale elastic pool
34+
35+
You can use the Azure CLI or Azure PowerShell to create a Hyperscale elastic pool.
36+
37+
### [Azure CLI](#tab/azure-cli)
38+
39+
40+
Use the [az sql elastic-pool create](/cli/azure/sql/elastic-pool#az_sql_elastic_pool_create) command to create a Hyperscale elastic pool.
41+
42+
The following example creates a Hyperscale elastic pool with 4 vCores, and two secondary pool replicas:
43+
44+
```azurecli
45+
az sql elastic-pool create --resource-group "my-example-rg" --server "my-example-sql-svr" --name "my_hs_pool" --edition "Hyperscale" --capacity 4 --family Gen5 --ha-replicas 2
46+
```
47+
48+
### [PowerShell](#tab/azure-powershell)
49+
50+
Use the [New-AzSqlElasticPool](/powershell/module/az.sql/new-azsqlelasticpool) cmdlet to create a Hyperscale elastic pool.
51+
52+
The following example creates a Hyperscale elastic pool configured with 4 vCores, and two secondary pool replicas:
53+
54+
```powershell
55+
New-AzSqlElasticPool -ResourceGroupName "my-example-rg" -ServerName "my-example-sql-svr" -ElasticPoolName "my_hs_pool" -Edition "Hyperscale" -VCore 4 -ComputeGeneration Gen5 -HighAvailabilityReplicaCount 2
56+
```
57+
58+
---
59+
60+
## Scale up a Hyperscale elastic pool
61+
62+
You can use the Azure CLI or Azure PowerShell to scale up an existing Hyperscale elastic pool.
63+
64+
65+
### [Azure CLI](#tab/azure-cli)
66+
67+
Use the [az sql elastic-pool update](/cli/azure/sql/elastic-pool#az-sql-elastic-pool-update) command to scale up an existing Hyperscale elastic pool.
68+
69+
The following example scales up an existing Hyperscale elastic pool to 8 vCores and sets the per-DB min and max to 0 and 2, respectively:
70+
71+
```azurecli
72+
az sql elastic-pool update --resource-group "my-example-rg" --server "my-example-sql-svr" --name "my_hs_pool" --capacity 8 --db-min-capacity 0 --db-max-capacity 2
73+
```
74+
75+
### [PowerShell](#tab/azure-powershell)
76+
77+
Use the [Set-AzSqlElasticPool](/powershell/module/az.sql/set-azsqlelasticpool) cmdlet to scale up an existing Hyperscale elastic pool.
78+
79+
The following example scales up an existing Hyperscale elastic pool to 8 vCores and sets the per-DB min and max to 0 and 2, respectively:
80+
81+
82+
```powershell
83+
Set-AzSqlElasticPool -ResourceGroupName "my-example-rg" -ServerName "my-example-sql-svr" -ElasticPoolName "my_hs_pool" -VCore 8 -DatabaseVCoreMin 0 -DatabaseVCoreMax 2
84+
```
85+
86+
---
87+
88+
## Scale out (or in) a Hyperscale elastic pool
89+
90+
Use the Azure CLI or Azure PowerShell to add or remove secondary pool replicas for an existing Hyperscale elastic pool - also known as scaling out or scaling in.
91+
92+
93+
### [Azure CLI](#tab/azure-cli)
94+
95+
Use the [az sql elastic-pool update](/cli/azure/sql/elastic-pool#az-sql-elastic-pool-update) command to scale out an existing Hyperscale elastic pool by adding a secondary pool replica or scale in an elastic pool by removing secondary pool replicas.
96+
97+
The following example scales out an existing Hyperscale elastic pool to use four secondary pool replicas:
98+
99+
```azurecli
100+
# use the --ha-replicas (--read-replicas can also be used) parameter to specify the new number of high-availability replicas:
101+
az sql elastic-pool update --resource-group "my-example-rg" --server "my-example-sql-svr" --name "my_hs_pool" --ha-replicas 4
102+
```
103+
104+
The following example scales in an existing Hyperscale elastic pool to use one secondary pool replica:
105+
106+
```azurecli
107+
# use the --ha-replicas (--read-replicas can also be used) parameter to specify the new number of high-availability replicas:
108+
az sql elastic-pool update --resource-group "my-example-rg" --server "my-example-sql-svr" --name "my_hs_pool" --ha-replicas 1
109+
```
110+
111+
### [PowerShell](#tab/azure-powershell)
112+
113+
Use the [Set-AzSqlElasticPool](/powershell/module/az.sql/set-azsqlelasticpool) command to scale out an existing Hyperscale elastic pool by adding a secondary pool replica or scale in an elastic pool by removing secondary pool replicas.
114+
115+
The following example scales out an existing Hyperscale elastic pool to use four secondary pool replicas:
116+
117+
```powershell
118+
Set-AzSqlElasticPool -ResourceGroupName "my-example-rg" -ServerName "my-example-sql-svr" -ElasticPoolName "my_hs_pool" -HighAvailabilityReplicaCount 4
119+
```
120+
121+
The following example scales in an existing Hyperscale elastic pool to use one secondary pool replica:
122+
123+
```powershell
124+
Set-AzSqlElasticPool -ResourceGroupName "my-example-rg" -ServerName "my-example-sql-svr" -ElasticPoolName "my_hs_pool" -HighAvailabilityReplicaCount 1
125+
```
126+
127+
---
128+
129+
## Move an existing database to a Hyperscale elastic pool
130+
131+
You can use the Azure CLI or Azure PowerShell to move an existing database in Azure SQL Database into an existing Hyperscale elastic pool.
132+
133+
### [Azure CLI](#tab/azure-cli)
134+
135+
Use the [az sql db update](/cli/azure/sql/db#az-sql-db-update) command to move an existing database into an existing Hyperscale elastic pool.
136+
137+
The following example moves database `my_existing_db` into existing Hyperscale elastic pool `my_hs_pool`:
138+
139+
```azurecli
140+
az sql db update --resource-group "my-example-rg" --server "my-example-sql-svr" --name "my_existing_db" --elastic-pool "my_hs_pool"
141+
```
142+
143+
### [PowerShell](#tab/azure-powershell)
144+
145+
Use the the [Set-AzSqlDatabase](/powershell/module/az.sql/set-azsqldatabase) cmdlet to move an existing database into an existing Hyperscale elastic pool.
146+
147+
148+
The following example moves database `my_existing_db` into existing Hyperscale elastic pool `my_hs_pool`:
149+
150+
```powershell
151+
Set-AzSqlDatabase -ResourceGroupName "my-example-rg" -ServerName "my-example-sql-svr" -DatabaseName "my_existing_db" -ElasticPoolName "my_hs_pool"
152+
```
153+
154+
---
155+
156+
## REST API
157+
158+
Use the [2021-11-01-preview](/rest/api/sql/2021-11-01-preview/elastic-pools/update?tabs=HTTP#update-high-availability-replica-count-of-a-hyperscale-elastic-pool) REST API (or later) to work with secondary replicas for Hyperscale elastic pools.
159+
160+
The following example scales out an existing Hyperscale elastic pool to use 4 secondary replicas:
161+
162+
```rest
163+
PATCH https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/elasticPools/{elasticPoolName}?api-version=2021-11-01-preview
164+
165+
{
166+
"properties": {
167+
"highAvailabilityReplicaCount": 4
168+
}
169+
}
170+
```
171+
172+
## Next steps
173+
174+
- [Azure SQL Database CLI commands](/cli/azure/sql).
175+
- [Azure SQL Database PowerShell cmdlets](/powershell/module/az.sql/).
176+
- [Azure SQL Database elastic pools REST API](/rest/api/sql/2021-11-01-preview/elastic-pools/).

0 commit comments

Comments
 (0)