Skip to content

Commit 228d8d8

Browse files
authored
Merge pull request #78957 from oslake/sqldb-serverless-2019.06.06
Fixed a bug
2 parents f238eaa + 80dc05c commit 228d8d8

File tree

2 files changed

+17
-17
lines changed

2 files changed

+17
-17
lines changed

articles/sql-database/sql-database-serverless.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,8 @@ A database in the serverless compute tier is parameterized by the compute range
3232

3333
- The total bill for a serverless database is the summation of the compute bill and storage bill.
3434
Billing for compute is based on the amount of vCores used and memory used per second.
35-
- The minimum compute billed is based on min vCores and min memory.
36-
- While the database is paused, only storage is billed.
35+
- The minimum amount of compute billed is based on min vCores and min memory.
36+
- Only storage is billed while the database is paused.
3737

3838
## Scenarios
3939

@@ -67,7 +67,7 @@ The following table summarizes distinctions between the serverless compute tier
6767

6868
SQL Database serverless is currently only supported in the General Purpose tier on Generation 5 hardware in the vCore purchasing model.
6969

70-
## Autoscale
70+
## Autoscaling
7171

7272
### Scaling responsiveness
7373

@@ -92,9 +92,9 @@ In both serverless and provisioned compute databases, cache entries may be evict
9292

9393
The SQL cache grows as data is fetched from disk in the same way and with the same speed as for provisioned databases. When the database is busy, the cache is allowed to grow unconstrained up to the max memory limit.
9494

95-
## Autopause and autoresume
95+
## Autopausing and autoresuming
9696

97-
### Autopause
97+
### Autopausing
9898

9999
Autopausing is triggered if all of the following conditions are true for the duration of the autopause delay:
100100

@@ -111,7 +111,7 @@ The following features do not support autopausing. That is, if any of the follo
111111

112112
Autopausing is temporarily prevented during the deployment of some service updates which require the database be online. In such cases, autopausing becomes allowed again once the service update completes.
113113

114-
### Autoresume
114+
### Autoresuming
115115

116116
Autoresuming is triggered if any of the following conditions are true at any time:
117117

@@ -142,7 +142,7 @@ The latency to autoresume and autopause a serverless database is generally order
142142

143143
## Onboarding into serverless compute tier
144144

145-
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:
145+
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.
146146

147147
1. Specify the service objective name. The service objective prescribes the service tier, hardware generation, and max vCores. The following table shows the service objective options:
148148

@@ -157,18 +157,18 @@ Creating a new database or moving an existing database into a serverless compute
157157
|Parameter|Value choices|Default value|
158158
|---|---|---|---|
159159
|Min vCores|Any of {0.5, 1, 2, 4} not exceeding max vCores|0.5 vCores|
160-
|Autopause delay|Min: 360 minutes (6 hours)<br>Max: 10080 minutes (7 days)<br>Increments: 60 minutes<br>Disable autopause: -1|360 minutes|
160+
|Autopause delay|Minimum: 360 minutes (6 hours)<br>Maximum: 10080 minutes (7 days)<br>Increments: 60 minutes<br>Disable autopause: -1|360 minutes|
161161

162162
> [!NOTE]
163163
> Using T-SQL to move an existing database into serverless or change its compute size is not currently supported but can be done via the Azure portal or PowerShell.
164164
165-
### Create new serverless database using Azure portal
165+
### Create new database in serverless compute tier using Azure portal
166166

167167
See [Quickstart: Create a single database in Azure SQL Database using the Azure portal](sql-database-single-database-get-started.md).
168168

169-
### Create new serverless database using PowerShell
169+
### Create new database in serverless compute tier using PowerShell
170170

171-
The following example creates a new database in the serverless compute tier defined by service objective named GP_S_Gen5_4 with default values for the min vCores and autopause delay.
171+
The following example creates a new database in the serverless compute tier. This example explicitly specifies the min vCores, max vCores, and autopause delay.
172172

173173
```powershell
174174
New-AzSqlDatabase `
@@ -183,9 +183,9 @@ New-AzSqlDatabase `
183183
-AutoPauseDelayInMinutes 720
184184
```
185185

186-
### Move provisioned compute database into serverless compute tier
186+
### Move database from provisioned compute tier into serverless compute tier
187187

188-
The following example moves an existing single database from the provisioned compute tier into the serverless compute tier. This example explicitly specifies the min vCores, max vCores, and autopause delay.
188+
The following example moves a database from the provisioned compute tier into the serverless compute tier. This example explicitly specifies the min vCores, max vCores, and autopause delay.
189189

190190
```powershell
191191
Set-AzSqlDatabase
@@ -200,7 +200,7 @@ Set-AzSqlDatabase
200200
-AutoPauseDelayInMinutes 1440
201201
```
202202

203-
### Move serverless database into provisioned compute tier
203+
### Move database from serverless compute tier into provisioned compute tier
204204

205205
A serverless database can be moved into a provisioned compute tier in the same way as moving a provisioned compute database into a serverless compute tier.
206206

@@ -222,7 +222,7 @@ Modifying the autopause delay is performed by using the [Set-AzSqlDatabase](http
222222

223223
### Resources used and billed
224224

225-
The resources of a serverless database are encapsulated by the following entities:
225+
The resources of a serverless database are encapsulated by app package, SQL instance, and user resource pool entities.
226226

227227
#### App package
228228

articles/sql-database/sql-database-single-database-get-started.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.devlang:
99
ms.topic: quickstart
1010
author: sachinpMSFT
1111
ms.author: ninarn
12-
ms.reviewer: carlrab
12+
ms.reviewer: carlrab, sstein
1313
manager: craigg
1414
ms.date: 04/23/2019
1515
---
@@ -131,4 +131,4 @@ When you're finished using these resources, you can delete them as follows:
131131
- [Connect and query using Azure Data Studio](https://docs.microsoft.com/sql/azure-data-studio/quickstart-sql-database?toc=/azure/sql-database/toc.json)
132132
- To create a single database in the provisioned compute tier using Azure CLI, see [Azure CLI samples](sql-database-cli-samples.md).
133133
- To create a single database in the provisioned compute tier using Azure PowerShell, see [Azure PowerShell samples](sql-database-powershell-samples.md).
134-
- To create a single database in the serverless compute tier using Azure Powershell, see [Create serverless database using PowerShell](sql-database-serverless.md#create-new-serverless-database-using-powershell)
134+
- To create a single database in the serverless compute tier using Azure Powershell, see [Create serverless database using PowerShell](sql-database-serverless.md#create-new-database-in-serverless-compute-tier-using-powershell)

0 commit comments

Comments
 (0)