Skip to content

Commit 6c19c81

Browse files
arvindshmicrosoftarvindshmicrosoft
committed
Fix legitimate Acrolinx correctness issues
1 parent 1e6cc24 commit 6c19c81

6 files changed

Lines changed: 46 additions & 46 deletions

‎azure-sql/azure-sql-iaas-vs-paas-what-is-overview.md‎

Lines changed: 14 additions & 14 deletions
Large diffs are not rendered by default.

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,11 +58,11 @@ The following figure shows an example of a database that spends much of its time
5858

5959
![Chart that shows a single database suitable for a pool.](./media/elastic-pool-overview/one-database.png)
6060

61-
The chart illustrates DTU usage over one hour from 12:00 to 1:00 where each data point has one-minute granularity. At 12:10, DB1 peaks up to 90 DTUs, but its overall average usage is less than five DTUs. An S3 compute size is required to run this workload in a single database, but this size leaves most of the resources unused during periods of low activity.
61+
The chart illustrates DTU usage over one hour from 12:00 to 1:00 where each data point has one-minute granularity. At 12:10, DB1 peaks up to 90 DTUs, but its overall average usage is fewer than five DTUs. An S3 compute size is required to run this workload in a single database, but this size leaves most of the resources unused during periods of low activity.
6262

6363
A pool allows these unused DTUs to be shared across multiple databases. A pool reduces the DTUs needed and the overall cost.
6464

65-
Building on the previous example, suppose there are other databases with similar utilization patterns as DB1. In the next two figures, the utilization of four databases and 20 databases are layered onto the same graph to illustrate the nonoverlapping nature of their utilization over time by using the DTU-based purchasing model:
65+
Building on the previous example, suppose there are other databases with similar utilization patterns as DB1. In the next two figures, the utilization of 4 databases and 20 databases are layered onto the same graph to illustrate the nonoverlapping nature of their utilization over time by using the DTU-based purchasing model:
6666

6767
![Chart that shows four databases with a utilization pattern suitable for a pool.](./media/elastic-pool-overview/four-databases.png)
6868

‎azure-sql/database/hyperscale-elastic-pool-command-line.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ az sql db update --resource-group "my-example-rg" --server "my-example-sql-svr"
140140

141141
### [PowerShell](#tab/azure-powershell)
142142

143-
Use the the [Set-AzSqlDatabase](/powershell/module/az.sql/set-azsqldatabase) cmdlet to move an existing database into an existing Hyperscale elastic pool.
143+
Use the [Set-AzSqlDatabase](/powershell/module/az.sql/set-azsqldatabase) cmdlet to move an existing database into an existing Hyperscale elastic pool.
144144

145145

146146
The following example moves database `my_existing_db` into existing Hyperscale elastic pool `my_hs_pool`:
@@ -155,7 +155,7 @@ Set-AzSqlDatabase -ResourceGroupName "my-example-rg" -ServerName "my-example-sql
155155

156156
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.
157157

158-
The following example scales out an existing Hyperscale elastic pool to use 4 secondary replicas:
158+
The following example scales out an existing Hyperscale elastic pool to use four secondary replicas:
159159

160160
```rest
161161
PATCH https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Sql/servers/{serverName}/elasticPools/{elasticPoolName}?api-version=2021-11-01-preview

0 commit comments

Comments
 (0)