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: articles/sql-database/sql-database-serverless.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,8 +32,8 @@ A database in the serverless compute tier is parameterized by the compute range
32
32
33
33
- The total bill for a serverless database is the summation of the compute bill and storage bill.
34
34
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.
37
37
38
38
## Scenarios
39
39
@@ -67,7 +67,7 @@ The following table summarizes distinctions between the serverless compute tier
67
67
68
68
SQL Database serverless is currently only supported in the General Purpose tier on Generation 5 hardware in the vCore purchasing model.
69
69
70
-
## Autoscale
70
+
## Autoscaling
71
71
72
72
### Scaling responsiveness
73
73
@@ -92,9 +92,9 @@ In both serverless and provisioned compute databases, cache entries may be evict
92
92
93
93
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.
94
94
95
-
## Autopause and autoresume
95
+
## Autopausing and autoresuming
96
96
97
-
### Autopause
97
+
### Autopausing
98
98
99
99
Autopausing is triggered if all of the following conditions are true for the duration of the autopause delay:
100
100
@@ -111,7 +111,7 @@ The following features do not support autopausing. That is, if any of the follo
111
111
112
112
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.
113
113
114
-
### Autoresume
114
+
### Autoresuming
115
115
116
116
Autoresuming is triggered if any of the following conditions are true at any time:
117
117
@@ -142,7 +142,7 @@ The latency to autoresume and autopause a serverless database is generally order
142
142
143
143
## Onboarding into serverless compute tier
144
144
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.
146
146
147
147
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:
148
148
@@ -157,18 +157,18 @@ Creating a new database or moving an existing database into a serverless compute
157
157
|Parameter|Value choices|Default value|
158
158
|---|---|---|---|
159
159
|Min vCores|Any of {0.5, 1, 2, 4} not exceeding max vCores|0.5 vCores|
> 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.
164
164
165
-
### Create new serverless database using Azure portal
165
+
### Create new database in serverless compute tier using Azure portal
166
166
167
167
See [Quickstart: Create a single database in Azure SQL Database using the Azure portal](sql-database-single-database-get-started.md).
168
168
169
-
### Create new serverless database using PowerShell
169
+
### Create new database in serverless compute tier using PowerShell
170
170
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.
172
172
173
173
```powershell
174
174
New-AzSqlDatabase `
@@ -183,9 +183,9 @@ New-AzSqlDatabase `
183
183
-AutoPauseDelayInMinutes 720
184
184
```
185
185
186
-
### Move provisioned compute database into serverless compute tier
186
+
### Move database from provisioned compute tier into serverless compute tier
187
187
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.
189
189
190
190
```powershell
191
191
Set-AzSqlDatabase
@@ -200,7 +200,7 @@ Set-AzSqlDatabase
200
200
-AutoPauseDelayInMinutes 1440
201
201
```
202
202
203
-
### Move serverless database into provisioned compute tier
203
+
### Move database from serverless compute tier into provisioned compute tier
204
204
205
205
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.
206
206
@@ -222,7 +222,7 @@ Modifying the autopause delay is performed by using the [Set-AzSqlDatabase](http
222
222
223
223
### Resources used and billed
224
224
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.
Copy file name to clipboardExpand all lines: articles/sql-database/sql-database-single-database-get-started.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.devlang:
9
9
ms.topic: quickstart
10
10
author: sachinpMSFT
11
11
ms.author: ninarn
12
-
ms.reviewer: carlrab
12
+
ms.reviewer: carlrab, sstein
13
13
manager: craigg
14
14
ms.date: 04/23/2019
15
15
---
@@ -131,4 +131,4 @@ When you're finished using these resources, you can delete them as follows:
131
131
-[Connect and query using Azure Data Studio](https://docs.microsoft.com/sql/azure-data-studio/quickstart-sql-database?toc=/azure/sql-database/toc.json)
132
132
- To create a single database in the provisioned compute tier using Azure CLI, see [Azure CLI samples](sql-database-cli-samples.md).
133
133
- 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