Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 09867d6

Browse files
committed
adding commands
fixing link fixing typo fixing moar things adding info to copy section fixing code block
1 parent 8358fdb commit 09867d6

4 files changed

Lines changed: 110 additions & 58 deletions

File tree

azure-sql/database/migrate-dtu-to-vcore.md

Lines changed: 48 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ description: Migrate a database in Azure SQL Database from the DTU model to the
44
author: dimitri-furman
55
ms.author: dfurman
66
ms.reviewer: wiassaf, mathoma, moslake
7-
ms.date: 04/10/2023
7+
ms.date: 03/27/2024
88
ms.service: sql-database
99
ms.subservice: service-overview
1010
ms.topic: conceptual
11-
ms.custom: sqldbrb=1
11+
ms.custom:
1212
---
1313
# Migrate Azure SQL Database from the DTU-based model to the vCore-based model
1414
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -19,14 +19,54 @@ This article describes how to migrate your database in Azure SQL Database from t
1919

2020
Migrating a database from the DTU-based purchasing model to the vCore-based purchasing model is similar to scaling between service objectives in the Basic, Standard, and Premium service tiers, with similar [duration](single-database-scale.md#latency) and a [minimal downtime](scale-resources.md) at the end of the migration process. A database migrated to the vCore-based purchasing model can be migrated back to the DTU-based purchasing model at any time using the same steps, except for databases migrated to the [Hyperscale](service-tier-hyperscale.md) service tier.
2121

22-
To migrate your database in the Azure portal, follow these steps:
22+
You can migrate your database to a different purchasing model by using the Azure portal, PowerShell, the Azure CLI, and Transact-SQL.
23+
24+
### [Azure portal](#tab/azure-portal)
25+
26+
To migrate your database to a different purchasing model by using the Azure portal, follow these steps:
2327

2428
1. Go to your SQL database in the [Azure portal](https://portal.azure.com).
2529
1. Select **Compute + storage** under **Settings**.
2630
1. Use the drop-down under **Service tier** to select a new purchasing model and service tier:
2731

2832
:::image type="content" source="media/migrate-dtu-to-vcore/migrate-purchasing-model-portal.png" alt-text="Screenshot of the compute + storage page of the SQL database in the Azure portal with Service tier selected." lightbox="media/migrate-dtu-to-vcore/migrate-purchasing-model-portal.png":::
2933

34+
### [PowerShell](#tab/powershell)
35+
36+
To migrate your database to a different purchasing model by using PowerShell, use [Set-AzSqlDatabase](/powershell/module/az.sql/set-azsqldatabase) such as the following sample:
37+
38+
```powershell-interactive
39+
$parameters = @{
40+
ResourceGroupName = "<resource group name>"
41+
DatabaseName = "<database name>"
42+
ServerName = "<server name>"
43+
Edition = "<service tier, such as Hyperscale>"
44+
RequestedServiceObjectiveName = "<hardware such as HS_Gen5_2>"
45+
}
46+
47+
Set-AzSqlDatabase @parameters
48+
```
49+
50+
51+
### [Azure CLI](#tab/azure-cli)
52+
53+
To migrate your database to a different purchasing model by using the Azure CLI, use [az sql db update](/cli/azure/sql/db#az-sql-db-update) such as the following sample:
54+
55+
```azurecli-interactive
56+
az sql db update --resource-group "<resource group name>" --server "<server name>" --name "<database name>" --edition <service tier, such as Hyperscale> --capacity 4 --family Gen5
57+
```
58+
59+
### [Transact-SQL](#tab/tsql)
60+
61+
62+
To migrate your database to a different purchasing model by using Transact-SQL, use [ALTER DATABASE](/sql/t-sql/statements/alter-database-transact-sql) such as the following sample:
63+
64+
```tsql
65+
ALTER DATABASE <database name> MODIFY (EDITION = '<service tier, such as Hyperscale>');
66+
```
67+
68+
---
69+
3070
## Choose the vCore service tier and service objective
3171

3272
For most DTU to vCore migration scenarios, databases and elastic pools in the Basic and Standard service tiers will map to the [General Purpose](service-tier-general-purpose.md) service tier. Databases and elastic pools in the Premium service tier will map to the [Business Critical](service-tier-business-critical.md) service tier. Depending on application scenario and requirements, the [Hyperscale](service-tier-hyperscale.md) service tier can often be used as the migration target for databases and elastic pools in all DTU service tiers.
@@ -199,7 +239,11 @@ If you're creating a geo-secondary in the elastic pool for a single primary data
199239

200240
## Use database copy to migrate from DTU to vCore
201241

202-
You can copy any database with a DTU-based compute size to a database with a vCore-based compute size without restrictions or special sequencing as long as the target compute size supports the maximum database size of the source database. Database copy creates a transactionally consistent snapshot of the data as of a point in time after the copy operation starts. It doesn't synchronize data between the source and the target after that point in time.
242+
[Database copy](database-copy.md) creates a transactionally consistent snapshot of the data at a point in time after the copy operation starts. It doesn't synchronize data between the source and the target after that point in time.
243+
244+
You can copy any database with a DTU-based compute size to a database with a vCore-based compute size by using PowerShell, the Azure CLI, or Transact-SQL without restrictions or special sequencing, as long as the target compute size supports the maximum database size of the source database. Copying a database to a different service tier isn't supported in the Azure portal.
245+
246+
203247

204248
## Next steps
205249

azure-sql/managed-instance/high-availability-sla.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ monikerRange: "= azuresql || = azuresql-mi"
2323
This article describes high availability in Azure SQL Managed Instance.
2424

2525
> [!IMPORTANT]
26-
> Zone-redundant configuration is in public preview for the General Purpose service tier and generaly available for the Business Critical service tier.
26+
> Zone-redundant configuration is in public preview for the General Purpose service tier and generally available for the Business Critical service tier.
2727
2828
## Overview
2929

docs/database-engine/availability-groups/windows/monitoring-of-availability-groups-sql-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ helpviewer_keywords:
1717

1818
|Tool|Brief Description|Links|
1919
|----------|-----------------------|-----------|
20-
|System Center Monitoring pack for SQL Server|The Monitoring pack for SQL Server (SQLMP) is the recommended solution for monitoring availability groups, availability replica and availability databases for IT administrators. Monitoring features that are particularly relevance to [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] include the following:<br /><br /> Automatic discoverability of availability groups, availability replicas, and availability database from among hundreds of computers. This enables you to easily keep track of your [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] inventory.<br /><br /> Fully capable System Center Operations Manager (SCOM) alerting and ticketing. These features provide detailed knowledge that enables faster resolution to a problem.<br /><br /> A custom extension to Always On Health monitoring using Policy Based management (PBM).<br /><br /> Health roll ups from availability databases to availability replicas.<br /><br /> Custom tasks that manage [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] from the System Center Operations Manager console.|To download the monitoring pack (SQLServerMP.msi) and *SQL Server Management Pack Guide for System Center Operations Manager* (SQLServerMPGuide.doc), see:<br /><br /> [System Center Monitoring pack for SQL Server](https://www.microsoft.com/download/details.aspx?id=56203)|
20+
|System Center Monitoring pack for SQL Server|The Monitoring pack for SQL Server (SQLMP) is the recommended solution for monitoring availability groups, availability replicas and availability databases for IT administrators. Monitoring features that are particularly relevant to [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] include the following:<br /><br /> Automatic discoverability of availability groups, availability replicas, and availability database from among hundreds of computers. This enables you to easily keep track of your [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] inventory.<br /><br /> Fully capable System Center Operations Manager (SCOM) alerting and ticketing. These features provide detailed knowledge that enables faster resolution to a problem.<br /><br /> A custom extension to Always On Health monitoring using Policy Based management (PBM).<br /><br /> Health roll ups from availability databases to availability replicas.<br /><br /> Custom tasks that manage [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] from the System Center Operations Manager console.|To download the monitoring pack (SQLServerMP.msi) and *SQL Server Management Pack Guide for System Center Operations Manager* (SQLServerMPGuide.doc), see:<br /><br /> [System Center Monitoring pack for SQL Server](https://www.microsoft.com/download/details.aspx?id=56203)|
2121
|[!INCLUDE[tsql](../../../includes/tsql-md.md)]|[!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] catalog and dynamic management views provide a wealth of information about your availability groups and their replicas, databases, listeners, and WSFC cluster environment.|[Monitor Availability Groups &#40;Transact-SQL&#41;](../../../database-engine/availability-groups/windows/monitor-availability-groups-transact-sql.md)|
2222
|[!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)]|The **Object Explorer Details** pane displays basic information about the availability groups hosted on the instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] to which you are connected.<br /><br /> **\*\* Tip \*\*** Use this pane to select multiple availability groups, replicas, or databases and to perform routine administrative tasks on the selected objects; for example, removing multiple availability replicas or databases from an availability group.|[Use the Object Explorer Details to Monitor Availability Groups &#40;SQL Server Management Studio&#41;](../../../database-engine/availability-groups/windows/use-object-explorer-details-to-monitor-availability-groups.md)|
2323
|[!INCLUDE[ssManStudioFull](../../../includes/ssmanstudiofull-md.md)]|**Properties** dialog boxes enable you to view the properties of availability groups, replicas, or listeners and, in some cases, to change their values.|- [View Availability Group Properties &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/view-availability-group-properties-sql-server.md)<br />- [View Availability Replica Properties &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/view-availability-replica-properties-sql-server.md)<br />- [View Availability Group Listener Properties &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/view-availability-group-listener-properties-sql-server.md)|

0 commit comments

Comments
 (0)