Skip to content

Commit effa630

Browse files
Ja-DunnJa-Dunn
authored
Merge pull request #73776 from CarlRabeler/20190418morgan
[sql db] morgan
2 parents bd009ba + 76ef2f5 commit effa630

8 files changed

+42
-11
lines changed

‎articles/sql-database/media/sql-database-single-database-scale/cancel-ongoing-operation.png

11.6 KB
Loading

‎articles/sql-database/media/sql-database-single-database-scale/ongoing-operations-1.png

12.5 KB
Loading

‎articles/sql-database/media/sql-database-single-database-scale/ongoing-operations.png

12.5 KB
Loading

‎articles/sql-database/sql-database-dtu-resource-limits-elastic-pools.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ For SQL Database elastic pools, the following tables show the resources availabl
104104
|||||||
105105

106106
> [!IMPORTANT]
107-
> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see [P11-P15 current limitations](sql-database-single-database-scale.md#dtu-based-purchasing-model-limitations-of-p11-and-p15-when-the-maximum-size-greater-than-1-tb).
107+
> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see [P11-P15 current limitations](sql-database-single-database-scale.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).
108108
109109
If all DTUs of an elastic pool are used, then each database in the pool receives an equal amount of resources to process queries. The SQL Database service provides resource sharing fairness between databases by ensuring equal slices of compute time. Elastic pool resource sharing fairness is in addition to any amount of resource otherwise guaranteed to each database when the DTU min per database is set to a non-zero value.
110110

‎articles/sql-database/sql-database-dtu-resource-limits-single-databases.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ The following tables show the resources available for a single database at each
7777
\* From 1024 GB up to 4096 GB in increments of 256 GB
7878

7979
> [!IMPORTANT]
80-
> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see [P11-P15 current limitations](sql-database-single-database-scale.md#dtu-based-purchasing-model-limitations-of-p11-and-p15-when-the-maximum-size-greater-than-1-tb).
80+
> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see [P11-P15 current limitations](sql-database-single-database-scale.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).
8181
> [!NOTE]
8282
> For `tempdb` limits, see [tempdb limits](https://docs.microsoft.com/sql/relational-databases/databases/tempdb-database?view=sql-server-2017#tempdb-database-in-sql-database).
8383

‎articles/sql-database/sql-database-service-tiers-dtu.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Compute sizes are expressed in terms of Database Transaction Units (DTUs) for si
6666
|||||
6767

6868
> [!IMPORTANT]
69-
> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see [P11-P15 current limitations](sql-database-single-database-scale.md#dtu-based-purchasing-model-limitations-of-p11-and-p15-when-the-maximum-size-greater-than-1-tb).
69+
> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see [P11-P15 current limitations](sql-database-single-database-scale.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).
7070
> [!IMPORTANT]
7171
> Under some circumstances, you may need to shrink a database to reclaim unused space. For more information, see [manage file space in Azure SQL Database](sql-database-file-space-management.md).
7272

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ To create a single database containing the AdventureWorksLT sample data:
6565
> [!NOTE]
6666
> This quickstart uses the [DTU-based purchasing model](sql-database-service-tiers-dtu.md), but the [vCore-based purchasing model](sql-database-service-tiers-vcore.md) is also available.
6767
> [!IMPORTANT]
68-
> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see [P11-P15 current limitations](sql-database-single-database-scale.md#dtu-based-purchasing-model-limitations-of-p11-and-p15-when-the-maximum-size-greater-than-1-tb).
68+
> More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see [P11-P15 current limitations](sql-database-single-database-scale.md#p11-and-p15-constraints-when-max-size-greater-than-1-tb).
6969
7070

7171

‎articles/sql-database/sql-database-single-database-scale.md

Lines changed: 38 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,11 @@ ms.subservice: performance
77
ms.custom:
88
ms.devlang:
99
ms.topic: conceptual
10-
author: juliemsft
11-
ms.author: jrasnick
10+
author: stevestein
11+
ms.author: sstein
1212
ms.reviewer: carlrab
1313
manager: craigg
14-
ms.date: 03/20/2019
14+
ms.date: 04/18/2019
1515
---
1616
# Scale single database resources in Azure SQL Database
1717

@@ -21,7 +21,7 @@ This article describes how to scale the compute and storage resources available
2121
> [!IMPORTANT]
2222
> The PowerShell Azure Resource Manager module is still supported by Azure SQL Database, but all future development is for the Az.Sql module. For these cmdlets, see [AzureRM.Sql](https://docs.microsoft.com/powershell/module/AzureRM.Sql/). The arguments for the commands in the Az module and in the AzureRm modules are substantially identical.
2323
24-
## Change compute resources (vCores or DTUs)
24+
## Change compute size (vCores or DTUs)
2525

2626
After initially picking the number of vCores or DTUs, you can scale a single database up or down dynamically based on actual experience using the [Azure portal](sql-database-single-databases-manage.md#manage-an-existing-sql-database-server), [Transact-SQL](https://docs.microsoft.com/sql/t-sql/statements/alter-database-transact-sql?view=azuresqldb-current#examples-1), [PowerShell](/powershell/module/az.sql/set-azsqldatabase), the [Azure CLI](/cli/azure/sql/db#az-sql-db-update), or the [REST API](https://docs.microsoft.com/rest/api/sql/databases/update).
2727

@@ -61,6 +61,37 @@ The latency to change the service tier or rescale the compute size of a single d
6161
> [!TIP]
6262
> To monitor in-progress operations, see: [Manage operations using the SQL REST API](https://docs.microsoft.com/rest/api/sql/operations/list), [Manage operations using CLI](/cli/azure/sql/db/op), [Monitor operations using T-SQL](/sql/relational-databases/system-dynamic-management-views/sys-dm-operation-status-azure-sql-database) and these two PowerShell commands: [Get-AzSqlDatabaseActivity](/powershell/module/az.sql/get-azsqldatabaseactivity) and [Stop-AzSqlDatabaseActivity](/powershell/module/az.sql/stop-azsqldatabaseactivity).
6363
64+
### Cancelling service tier changes or compute rescaling operations
65+
66+
A service tier change or compute rescaling operation can be cancelled.
67+
68+
#### Azure portal
69+
70+
In the database overview blade, navigate to **Notifications** and click on the tile indicating there is an ongoing operation:
71+
72+
![Ongoing operation](media/sql-database-single-database-scale/ongoing-operations.png)
73+
74+
Next, click on the button labeled **Cancel this operation**.
75+
76+
![Cancel ongoing operation](media/sql-database-single-database-scale/cancel-ongoing-operation.png)
77+
78+
#### PowerShell
79+
80+
From a PowerShell command prompt, set the `$ResourceGroupName`, `$ServerName`, and `$DatabaseName`, and then run the following command:
81+
82+
```PowerShell
83+
$OperationName = (az sql db op list --resource-group $ResourceGroupName --server $ServerName --database $DatabaseName --query "[?state=='InProgress'].name" --out tsv)
84+
if(-not [string]::IsNullOrEmpty($OperationName))
85+
{
86+
(az sql db op cancel --resource-group $ResourceGroupName --server $ServerName --database $DatabaseName --name $OperationName)
87+
"Operation " + $OperationName + " has been canceled"
88+
}
89+
else
90+
{
91+
"No service tier change or compute rescaling operation found"
92+
}
93+
```
94+
6495
### Additional considerations when changing service tier or rescaling compute size
6596

6697
- If you are upgrading to a higher service tier or compute size, the database max size does not increase unless you explicitly specify a larger size (maxsize).
@@ -71,7 +102,7 @@ The latency to change the service tier or rescale the compute size of a single d
71102
- The restore service offerings are different for the various service tiers. If you are downgrading to the **Basic** tier, there is a lower backup retention period. See [Azure SQL Database Backups](sql-database-automated-backups.md).
72103
- The new properties for the database are not applied until the changes are complete.
73104

74-
### Billing during rescaling
105+
### Billing during compute rescaling
75106

76107
You are billed for each hour a database exists using the highest service tier + compute size that applied during that hour, regardless of usage or whether the database was active for less than an hour. For example, if you create a single database and delete it five minutes later your bill reflects a charge for one database hour.
77108

@@ -97,9 +128,9 @@ You are billed for each hour a database exists using the highest service tier +
97128
> [!IMPORTANT]
98129
> Under some circumstances, you may need to shrink a database to reclaim unused space. For more information, see [Manage file space in Azure SQL Database](sql-database-file-space-management.md).
99130
100-
## DTU-based purchasing model: Limitations of P11 and P15 when the maximum size greater than 1 TB
131+
## P11 and P15 constraints when max size greater than 1 TB
101132

102-
More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. For more information, see [P11-P15 current limitations](sql-database-single-database-scale.md#dtu-based-purchasing-model-limitations-of-p11-and-p15-when-the-maximum-size-greater-than-1-tb). The following considerations and limitations apply to P11 and P15 databases with a maximum size greater than 1 TB:
133+
More than 1 TB of storage in the Premium tier is currently available in all regions except: China East, China North, Germany Central, Germany Northeast, West Central US, US DoD regions, and US Government Central. In these regions, the storage max in the Premium tier is limited to 1 TB. The following considerations and limitations apply to P11 and P15 databases with a maximum size greater than 1 TB:
103134

104135
- If the max size for a P11 or P15 database was ever set to a value greater than 1 TB, then can it only be restored or copied to a P11 or P15 database. Subsequently, the database can be rescaled to a different compute size provided the amount of space allocated at the time of the rescaling operation does not exceed max size limits of the new compute size.
105136
- For active geo-replication scenarios:

0 commit comments

Comments
 (0)