Skip to content

Commit 4578e90

Browse files
dimitri-furmandimitri-furman
committed
Removing "hardware generation"
1 parent 47fca02 commit 4578e90

19 files changed

Lines changed: 66 additions & 65 deletions

‎azure-sql/database/always-encrypted-enclaves-enable-sgx.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Enable Intel SGX for Always Encrypted"
3-
description: "Learn how to enable Intel SGX for Always Encrypted with secure enclaves in Azure SQL Database by selecting an SGX-enabled hardware generation."
3+
description: "Learn how to enable Intel SGX for Always Encrypted with secure enclaves in Azure SQL Database by selecting an SGX-enabled hardware."
44
services: sql-database
55
ms.service: sql-database
66
ms.subservice: security

‎azure-sql/database/always-encrypted-enclaves-getting-started.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: tutorial
99
author: jaszymas
1010
ms.author: jaszymas
1111
ms.reviwer: vanto
12-
ms.date: 07/14/2021
12+
ms.date: 04/06/2022
1313
---
1414
# Tutorial: Getting started with Always Encrypted with secure enclaves in Azure SQL Database
1515

@@ -53,7 +53,7 @@ To continue to interact with the PowerShell Gallery, run the following command b
5353

5454
## Step 1: Create and configure a server and a DC-series database
5555

56-
In this step, you will create a new Azure SQL Database logical server and a new database using the DC-series hardware generation, required for Always Encrypted with secure enclaves. For more information see [DC-series](service-tiers-sql-database-vcore.md#dc-series).
56+
In this step, you will create a new Azure SQL Database logical server and a new database using the DC-series hardware, required for Always Encrypted with secure enclaves. For more information see [DC-series](service-tiers-sql-database-vcore.md#dc-series).
5757

5858
# [Portal](#tab/azure-portal)
5959

@@ -72,7 +72,7 @@ In this step, you will create a new Azure SQL Database logical server and a new
7272
- **Password**: Enter a password that meets requirements, and enter it again in the **Confirm password** field.
7373
- **Location**: Select a location from the dropdown list.
7474
> [!IMPORTANT]
75-
> You need to select a location (an Azure region) that supports both the DC-series hardware generation and Microsoft Azure Attestation. For the list of regions supporting DC-series, see [DC-series availability](service-tiers-sql-database-vcore.md#dc-series). [Here](https://azure.microsoft.com/global-infrastructure/services/?products=azure-attestation) is the regional availability of Microsoft Azure Attestation.
75+
> You need to select a location (an Azure region) that supports both the DC-series hardware and Microsoft Azure Attestation. For the list of regions supporting DC-series, see [DC-series availability](service-tiers-sql-database-vcore.md#dc-series). [Here](https://azure.microsoft.com/global-infrastructure/services/?products=azure-attestation) is the regional availability of Microsoft Azure Attestation.
7676
7777
Select **OK**.
7878
1. Leave **Want to use SQL elastic pool** set to **No**.
@@ -117,7 +117,7 @@ In this step, you will create a new Azure SQL Database logical server and a new
117117
1. Create a new resource group.
118118

119119
> [!IMPORTANT]
120-
> You need to create your resource group in a region (location) that supports both the DC-series hardware generation and Microsoft Azure Attestation. For the list of regions supporting DC-series, see [DC-series availability](service-tiers-sql-database-vcore.md#dc-series). [Here](https://azure.microsoft.com/global-infrastructure/services/?products=azure-attestation) is the regional availability of Microsoft Azure Attestation.
120+
> You need to create your resource group in a region (location) that supports both the DC-series hardware and Microsoft Azure Attestation. For the list of regions supporting DC-series, see [DC-series availability](service-tiers-sql-database-vcore.md#dc-series). [Here](https://azure.microsoft.com/global-infrastructure/services/?products=azure-attestation) is the regional availability of Microsoft Azure Attestation.
121121
122122
```powershell
123123
$resourceGroupName = "<your new resource group name>"

‎azure-sql/database/always-encrypted-enclaves-plan.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: conceptual
99
author: jaszymas
1010
ms.author: jaszymas
1111
ms.reviwer: vanto
12-
ms.date: 07/14/2021
12+
ms.date: 04/06/2022
1313
---
1414

1515
# Plan for Intel SGX enclaves and attestation in Azure SQL Database
@@ -20,17 +20,17 @@ ms.date: 07/14/2021
2020

2121
## Plan for Intel SGX in Azure SQL Database
2222

23-
Intel SGX is a hardware-based trusted execution environment technology. Intel SGX is available for databases that use the [vCore model](service-tiers-sql-database-vcore.md) and the [DC-series](service-tiers-sql-database-vcore.md?#dc-series) hardware generation. Therefore, to ensure you can use Always Encrypted with secure enclaves in your database, you need to either select the DC-series hardware generation when you create the database, or you can update your existing database to use the DC-series hardware generation.
23+
Intel SGX is a hardware-based trusted execution environment technology. Intel SGX is available for databases that use the [vCore model](service-tiers-sql-database-vcore.md) and the [DC-series](service-tiers-sql-database-vcore.md?#dc-series) hardware. Therefore, to ensure you can use Always Encrypted with secure enclaves in your database, you need to either select the DC-series hardware when you create the database, or you can update your existing database to use the DC-series hardware.
2424

2525
> [!NOTE]
26-
> Intel SGX is not available in hardware generations other than DC-series. For example, Intel SGX is not available for Gen5 hardware, and it is not available for databases using the [DTU model](service-tiers-dtu.md).
26+
> Intel SGX is not available in hardware other than DC-series. For example, Intel SGX is not available for Gen5 hardware, and it is not available for databases using the [DTU model](service-tiers-dtu.md).
2727
2828
> [!IMPORTANT]
29-
> Before you configure the DC-series hardware generation for your database, check the regional availability of DC-series and make sure you understand its performance limitations. For details, see [DC-series](service-tiers-sql-database-vcore.md#dc-series).
29+
> Before you configure the DC-series hardware for your database, check the regional availability of DC-series and make sure you understand its performance limitations. For details, see [DC-series](service-tiers-sql-database-vcore.md#dc-series).
3030
3131
## Plan for attestation in Azure SQL Database
3232

33-
[Microsoft Azure Attestation](../../attestation/overview.md) is a solution for attesting Trusted Execution Environments (TEEs), including Intel SGX enclaves in Azure SQL databases using the DC-series hardware generation.
33+
[Microsoft Azure Attestation](../../attestation/overview.md) is a solution for attesting Trusted Execution Environments (TEEs), including Intel SGX enclaves in Azure SQL databases using the DC-series hardware.
3434

3535
To use Azure Attestation for attesting Intel SGX enclaves in Azure SQL Database, you need to create an [attestation provider](../../attestation/basic-concepts.md#attestation-provider) and configure it with the Microsoft-provided attestation policy. See [Configure attestation for Always Encrypted using Azure Attestation](always-encrypted-enclaves-configure-attestation.md)
3636

@@ -39,7 +39,7 @@ To use Azure Attestation for attesting Intel SGX enclaves in Azure SQL Database,
3939
Configuring your environment to support Intel SGX enclaves and attestation for Always Encrypted in Azure SQL Database involves setting up components of different types: Microsoft Azure Attestation, Azure SQL Database, and applications that trigger enclave attestation. Configuring components of each type is performed by users assuming one of the below distinct roles:
4040

4141
- Attestation administrator - creates an attestation provider in Microsoft Azure Attestation, authors the attestation policy, grants Azure SQL logical server access to the attestation provider, and shares the attestation URL that points to the policy to application administrators.
42-
- Azure SQL Database administrator - enables SGX enclaves in databases by selecting the DC-series hardware generation, and provides the attestation administrator with the identity of the Azure SQL logical server that needs to access the attestation provider.
42+
- Azure SQL Database administrator - enables SGX enclaves in databases by selecting the DC-series hardware, and provides the attestation administrator with the identity of the Azure SQL logical server that needs to access the attestation provider.
4343
- Application administrator - configures applications with the attestation URL obtained from the attestation administrator.
4444

4545
In production environments (handling real sensitive data), it is important your organization adheres to role separation when configuring attestation, where each distinct role is assumed by different people. In particular, if the goal of deploying Always Encrypted in your organization is to reduce the attack surface area by ensuring Azure SQL Database administrators cannot access sensitive data, Azure SQL Database administrators should not control attestation policies.

‎azure-sql/database/configure-max-degree-of-parallelism.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Configure the max degree of parallelism (MAXDOP)"
33
titleSuffix: Azure SQL Database
44
description: Learn about the max degree of parallelism (MAXDOP).
5-
ms.date: "04/12/2021"
5+
ms.date: "04/06/2022"
66
services: sql-database
77
dev_langs:
88
- "TSQL"
@@ -71,7 +71,7 @@ ms.reviewer: kendralittle, mathoma
7171
> [!Tip]
7272
> We recommend that customers avoid setting MAXDOP to 0 even if it does not appear to cause problems currently.
7373
74-
Excessive parallelism becomes most problematic when there are more concurrent requests than can be supported by the CPU and worker thread resources provided by the service objective. Avoid MAXDOP 0 to reduce the risk of potential future problems due to excessive parallelism if a database is scaled up, or if future hardware generations in Azure SQL Database provide more cores for the same database service objective.
74+
Excessive parallelism becomes most problematic when there are more concurrent requests than can be supported by the CPU and worker thread resources provided by the service objective. Avoid MAXDOP 0 to reduce the risk of potential future problems due to excessive parallelism if a database is scaled up, or if future hardware configurations in Azure SQL Database provide more cores for the same database service objective.
7575

7676
### Modifying MAXDOP
7777

‎azure-sql/database/gateway-migration.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,12 @@ ms.topic: conceptual
99
author: rohitnayakmsft
1010
ms.author: rohitna
1111
ms.reviewer: kendralittle, vanto, mathoma
12-
ms.date: 07/01/2019
12+
ms.date: 04/06/2022
1313
---
1414
# Azure SQL Database traffic migration to newer Gateways
1515
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
1616

17-
Microsoft periodically refreshes hardware to optimize the customer experience. During these refreshes, Azure adds gateways built on newer hardware generations, migrates traffic to them, and eventually decommissions gateways built on older hardware in some regions.
17+
Microsoft periodically refreshes hardware to optimize the customer experience. During these refreshes, Azure adds gateways built on newer hardware, migrates traffic to them, and eventually decommissions gateways built on older hardware in some regions.
1818

1919

2020
To avoid service disruptions during refreshes, allow the communication with SQL Gateway IP subnet ranges for the region. Review [SQL Gateway IP subnet ranges](connectivity-architecture.md#gateway-ip-addresses) and include the ranges for your region.

‎azure-sql/database/purchasing-models.md‎

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.topic: conceptual
1111
author: LitKnd
1212
ms.author: kendralittle
1313
ms.reviewer: mathoma
14-
ms.date: 02/02/2022
14+
ms.date: 04/06/2022
1515
---
1616
# Compare vCore and DTU-based purchasing models of Azure SQL Database
1717
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -47,10 +47,11 @@ In the vCore-based purchasing model for SQL Database, you can choose between the
4747

4848
In the vCore-based purchasing model, you pay for:
4949

50-
- Compute resources (the service tier + the number of vCores and the amount of memory + the generation of hardware).
51-
- The type and amount of data and log storage.
52-
- Backup storage.
53-
50+
- Service tier
51+
- Hardware configuration
52+
- Compute resources (the number of vCores and the amount of memory)
53+
- Reserved database storage
54+
- Actual backup storage
5455

5556
## DTU purchasing model
5657

‎azure-sql/database/quota-increase-request.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -105,11 +105,11 @@ If your subscription needs access in a particular region, select the **Region ac
105105

106106
### Request enabling specific hardware in a region
107107

108-
If a hardware generation you want to use is not available in your region, you may request it using the following steps. For more information on hardware generations and regional availability, see [Hardware generations for SQL Database](./service-tiers-sql-database-vcore.md#hardware-configuration) or [Hardware generations for SQL Managed Instance](../managed-instance/service-tiers-managed-instance-vcore.md#hardware-configurations).
108+
If the hardware you want to use is not available in your region, you may request it using the following steps. For more information on hardware regional availability, see [Hardware configurations for SQL Database](./service-tiers-sql-database-vcore.md#hardware-configuration) or [Hardware configurations for SQL Managed Instance](../managed-instance/service-tiers-managed-instance-vcore.md#hardware-configurations).
109109

110110
1. Select the **Other quota request** quota type.
111111

112-
1. In the **Description** field, state your request, including the name of the hardware generation and the name of the region you need it in.
112+
1. In the **Description** field, state your request, including the name of the hardware and the name of the region you need it in.
113113

114114
![Request hardware in a new region](./media/quota-increase-request/hardware-in-new-region.png)
115115

‎azure-sql/database/reserved-capacity-overview.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.topic: conceptual
1111
author: emlisa
1212
ms.author: emlisa
1313
ms.reviewer: kendralittle, mathoma
14-
ms.date: 10/13/2020
14+
ms.date: 04/06/2022
1515
---
1616
# Save costs for resources with reserved capacity - Azure SQL Database & SQL Managed Instance
1717
[!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
@@ -34,7 +34,7 @@ For more information about how enterprise customers and Pay-As-You-Go customers
3434
3535
## Determine correct size before purchase
3636

37-
The size of reservation should be based on the total amount of compute used by the existing or soon-to-be-deployed database or managed instance within a specific region and using the same performance tier and hardware generation.
37+
The size of reservation should be based on the total amount of compute used by the existing or soon-to-be-deployed database or managed instance within a specific region and using the same performance tier and hardware configuration.
3838

3939
For example, let's suppose that you are running one general purpose, Gen5 – 16 vCore elastic pool and two business critical Gen5 – 4 vCore single databases. Further, let's supposed that you plan to deploy within the next month an additional general purpose Gen5 – 16 vCore elastic pool and one business critical Gen5 – 32 vCore elastic pool. Also, let's suppose that you know that you will need these resources for at least 1 year. In this case, you should purchase a 32 (2x16) vCores 1-year reservation for single database/elastic pool general purpose - Gen5 and a 40 (2x4 + 32) vCore 1-year reservation for single database/elastic pool business critical - Gen5.
4040

‎azure-sql/database/serverless-tier-overview.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: conceptual
99
author: oslake
1010
ms.author: moslake
1111
ms.reviewer: kendralittle, mathoma, wiassaf
12-
ms.date: 9/28/2021
12+
ms.date: 04/06/2022
1313
---
1414
# Azure SQL Database serverless
1515
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -197,7 +197,7 @@ If using [customer managed transparent data encryption](transparent-data-encrypt
197197

198198
Creating a new database or moving an existing database into a serverless compute tier follows the same pattern as creating a new database in provisioned compute tier and involves the following two steps.
199199

200-
1. Specify the service objective. The service objective prescribes the service tier, hardware generation, and max vCores. For service objective options, see [serverless resource limits](resource-limits-vcore-single-databases.md#general-purpose---serverless-compute---gen5)
200+
1. Specify the service objective. The service objective prescribes the service tier, hardware configuration, and max vCores. For service objective options, see [serverless resource limits](resource-limits-vcore-single-databases.md#general-purpose---serverless-compute---gen5)
201201

202202

203203
2. Optionally, specify the min vCores and auto-pause delay to change their default values. The following table shows the available values for these parameters.

‎azure-sql/database/service-tiers-sql-database-vcore.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ This article reviews the [vCore purchasing model](service-tiers-vcore.md) for [A
3030
The vCore purchasing model used by Azure SQL Database provides several benefits over the DTU purchasing model:
3131

3232
- Higher compute, memory, I/O, and storage limits.
33-
- Control over the hardware generation to better match compute and memory requirements of the workload.
33+
- A degree of control over hardware to better match compute and memory requirements of the workload.
3434
- Pricing discounts for [Azure Hybrid Benefit (AHB)](../azure-hybrid-benefit.md).
3535
- Greater transparency in the hardware details that power the compute, that facilitates planning for migrations from on-premises deployments.
3636
- [Reserved instance pricing](reserved-capacity-overview.md) is only available for vCore purchasing model.
@@ -125,7 +125,7 @@ To create databases or elastic pools on DC-series hardware, the subscription mus
125125

126126
You can select hardware configuration for a database or elastic pool in SQL Database at the time of creation. You can also change hardware configuration of an existing database or elastic pool.
127127

128-
**To select a hardware generation when creating a SQL Database or pool**
128+
**To select a hardware configuration when creating a SQL Database or pool**
129129

130130
For detailed information, see [Create a SQL Database](single-database-create-quickstart.md).
131131

0 commit comments

Comments
 (0)