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: docs/azure-data-studio/azure-sql-managed-instance-extension.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Azure SQL Managed Instance extension
3
-
description: Use Azure Data Studio with Azure SQL managed instance
3
+
description: Use Azure Data Studio with Azure SQL Managed Instance
4
4
ms.custom: "seodec18"
5
5
ms.date: "10/07/2019"
6
6
ms.reviewer: alanyu, maghan, sstein
@@ -16,7 +16,7 @@ manager: alanyu
16
16
17
17
The Azure SQL Managed Instance extension provides a dashboard for working with an [Azure SQL Managed Instance](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance-index) in [Azure Data Studio](https://github.com/Microsoft/azuredatastudio). This extension provides the following features:
18
18
19
-
- Shows managed instance properties, including vCores and used storage
19
+
- Shows SQL Managed Instance properties, including vCores and used storage
20
20
- Monitors CPU and storage usage for previous two hours
21
21
- Displays configuration warnings and tuning recommendations
22
22
- Shows state of database replicas
@@ -26,7 +26,7 @@ The Azure SQL Managed Instance extension provides a dashboard for working with a
26
26
27
27
You can install the official release of this extension. Follow the steps
28
28
in the [Azure Data Studio documentation](https://docs.microsoft.com/sql/azure-data-studio/extensions).
29
-
In the **Extensions** pane, search for "managed instance", and install it there. After it's installed, you'll get notified automatically about any future extension updates.
29
+
In the **Extensions** pane, search for "Managed Instance", and install it there. After it's installed, you'll get notified automatically about any future extension updates.
30
30
31
31
With the extension installed, you'll see a **Managed Instance** tab in Azure Data Studio. Here you can find information specific for your managed instance.
Copy file name to clipboardExpand all lines: docs/azure-data-studio/faq.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -178,7 +178,7 @@ Developers and DBAs are usually the users of Azure Data Studio.
178
178
179
179
## Does Azure Data Studio integrate with Azure SQL Data Warehouse?
180
180
181
-
Yes. Azure Data Studio support for Azure SQL Data Warehouse is currently in preview, together with Azure SQL Database Managed Instance, and SQL Server 2019 Big Data.
181
+
Yes. Azure Data Studio support for Azure SQL Data Warehouse is currently in preview, together with Azure SQL Managed Instance, and SQL Server 2019 Big Data.
182
182
183
183
## Why is Azure Data Studio important for the new version of SQL Server?
Copy file name to clipboardExpand all lines: docs/database-engine/configure-windows/sql-server-service-broker.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: "SQL Server Service Broker | Microsoft Docs"
3
-
description: Learn about Service Broker. See how it provides native support for messaging in the SQL Server Database Engine and Azure SQL Database Managed Instance.
3
+
description: Learn about Service Broker. See how it provides native support for messaging in the SQL Server Database Engine and Azure SQL Managed Instance.
[!INCLUDE [SQL Server SQL MI](../../includes/applies-to-version/sql-asdbmi.md)]
30
30
31
-
[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)][!INCLUDE[ssSB](../../includes/sssb-md.md)] provide native support for messaging and queuing in the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] and [Azure SQL Database Managed Instance](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance-index). Developers can easily create sophisticated applications that use the [!INCLUDE[ssDE](../../includes/ssde-md.md)] components to communicate between disparate databases, and build distributed and reliable applications.
31
+
[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)][!INCLUDE[ssSB](../../includes/sssb-md.md)] provide native support for messaging and queuing in the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] and [Azure SQL Managed Instance](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance-index). Developers can easily create sophisticated applications that use the [!INCLUDE[ssDE](../../includes/ssde-md.md)] components to communicate between disparate databases, and build distributed and reliable applications.
32
32
33
33
## When to use Service Broker
34
34
@@ -97,7 +97,7 @@ FROM ExpenseQueue;
97
97
## What's new in Service Broker
98
98
No significant changes are introduced in [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]. The following changes were introduced in [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)].
99
99
100
-
### Service broker and Azure SQL Database Managed Instance
100
+
### Service broker and Azure SQL Managed Instance
101
101
102
102
- Cross-instance service broker is not supported
103
103
-`sys.routes` - Prerequisite: select address from sys.routes. Address must be LOCAL on every route. See [sys.routes](../../relational-databases/system-catalog-views/sys-routes-transact-sql.md).
Copy file name to clipboardExpand all lines: docs/dma/dma-assess-sql-data-estate-to-sqldb.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ After you successfully create a migration project, under **Assessment tools**, i
93
93
1. On the left, select the **+** icon, and then select the assessment **Project type**
94
94
2. Specify the project name, and then select the source server and target server types.
95
95
96
-
If you're upgrading your on-premises SQL Server instance to a later version of SQL Server or to SQL Server hosted on an Azure VM, set the source and target server type to **SQL Server**. Set the target server type to **Azure SQL Database Managed Instance** for an Azure SQL Database (PaaS) target readiness assessment.
96
+
If you're upgrading your on-premises SQL Server instance to a later version of SQL Server or to SQL Server hosted on an Azure VM, set the source and target server type to **SQL Server**. Set the target server type to **Azure SQL Managed Instance** for an Azure SQL Database (PaaS) target readiness assessment.
Copy file name to clipboardExpand all lines: docs/dma/dma-sku-recommend-sql-db.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,18 +20,18 @@ ms.author: rajpo
20
20
21
21
Migrating databases to the cloud can be complicated, especially when trying to select the best Azure database target and SKU for your database. Our goal with the Database Migration Assistant (DMA) is to help address these questions and make your database migration experience easier by providing these SKU recommendations in a user-friendly output.
22
22
23
-
This article focuses on DMA's Azure SQL Database SKU recommendations feature. Azure SQL Database has several deployment options, including:
23
+
This article focuses on DMA's Azure SQL Database SKU recommendations feature. Azure SQL Database and Azure SQL Managed Instance have several deployment options, including:
24
24
25
25
- Single database
26
26
- Elastic pools
27
27
- Managed instance
28
28
29
-
The SKU Recommendations feature allows you to identify both the minimum recommended Azure SQL Database single database or managed instance SKU based on performance counters collected from the computer(s) hosting your databases. The feature provides recommendations related to pricing tier, compute level, and max data size, as well as estimated cost per month. It also offers the ability to bulk provision single databases and managed instances in Azure for all recommended databases.
29
+
The SKU Recommendations feature allows you to identify both the minimum recommended Azure SQL Database single database or Azure SQL Managed Instance SKU based on performance counters collected from the computer(s) hosting your databases. The feature provides recommendations related to pricing tier, compute level, and max data size, as well as estimated cost per month. It also offers the ability to bulk provision single databases and managed instances for all recommended databases.
30
30
31
31
> [!NOTE]
32
32
> This functionality is currently available only via the Command Line Interface (CLI).
33
33
34
-
The following are instructions to help you determine the Azure SQL Database SKU recommendations and provision corresponding single database(s) or managed instance(s) in Azure using DMA.
34
+
The following are instructions to help you determine the SKU recommendations and provision corresponding single database(s) or managed instance(s) in Azure using DMA.
35
35
36
36
## Prerequisites
37
37
@@ -171,15 +171,15 @@ For managed instance recommendations, the TSV output file will look as follows:
171
171
A description of each column in the output file follows.
- **PricePerMonth** – The estimated price per month for the corresponding SKU.
177
177
- **RegionName** – The region name for the corresponding SKU.
178
178
- **IsTierRecommended** - We make a minimum SKU recommendation for each tier. We then apply heuristics to determine the right tier for your database. This reflects which tier is recommended for the database.
179
179
- **ExclusionReasons** - This value is blank if a Tier is recommended. For each tier that isn't recommended, we provide the reasons why it wasn't picked.
180
180
- **AppliedRules** - A short notation of the rules that were applied.
181
181
182
-
The final recommended tier (i.e., **MetricType**) and value (i.e., **MetricValue**) - found where the **IsTierRecommended** column is TRUE - reflects the minimum SKU required for your queries to run in Azure with a success rate similar to your on-premises databases. For managed instance, DMA currently supports recommendations for the most commonly used 8vcore to 40vcore SKUs. For example, if the recommended minimum SKU is S4 for the standard tier, then choosing S3 or below will cause queries to time out or fail to execute.
182
+
The final recommended tier (i.e., **MetricType**) and value (i.e., **MetricValue**) - found where the **IsTierRecommended** column is TRUE - reflects the minimum SKU required for your queries to run in Azure with a success rate similar to your on-premises databases. For Azure SQL Managed Instance, DMA currently supports recommendations for the most commonly used 8vcore to 40vcore SKUs. For example, if the recommended minimum SKU is S4 for the standard tier, then choosing S3 or below will cause queries to time out or fail to execute.
183
183
184
184
The HTML file contains this information in a graphical format. It provides a user-friendly means of viewing the final recommendation and provisioning the next part of the process. More information on the HTML output is in the following section.
185
185
@@ -209,7 +209,7 @@ To input provisioning information and make changes to the recommendations, updat
209
209
210
210
This process should create all the databases you selected in the HTML page.
Copy file name to clipboardExpand all lines: docs/dma/dma-whatsnew.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ The assessment workflow helps you detect the following issues, which can affect
78
78
- Behavioral changes: The schema objects reported may continue to work, but they may exhibit a different behavior, for example performance degradation.
79
79
- Informational issues: These objects won't impact the migration but may have been deprecated from feature SQL Server releases.
80
80
81
-
After the assessment is complete, use our [Azure Database Migration Service](https://azure.microsoft.com/services/database-migration/) (DMS) to perform the migration of your SQL Server databases to SQL Database Managed Instance. DMS supports both [offline](https://docs.microsoft.com/azure/dms/tutorial-sql-server-to-managed-instance) (one-time) and [online](https://docs.microsoft.com/azure/dms/tutorial-sql-server-managed-instance-online) (minimal-downtime) database migrations to SQL Database Managed Instance.
81
+
After the assessment is complete, use our [Azure Database Migration Service](https://azure.microsoft.com/services/database-migration/) (DMS) to perform the migration of your SQL Server databases to SQL Managed Instance. DMS supports both [offline](https://docs.microsoft.com/azure/dms/tutorial-sql-server-to-managed-instance) (one-time) and [online](https://docs.microsoft.com/azure/dms/tutorial-sql-server-managed-instance-online) (minimal-downtime) database migrations to SQL Managed Instance.
Copy file name to clipboardExpand all lines: docs/includes/create-workload-group.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ IMPORTANCE is local to the resource pool; workload groups of different importanc
41
41
REQUEST_MAX_MEMORY_GRANT_PERCENT = *value*</br>
42
42
Specifies the maximum amount of memory that a single request can take from the pool. *value* is a percentage relative to the resource pool size specified by MAX_MEMORY_PERCENT.
43
43
44
-
*value* is an integer up to [!INCLUDE[ssSQL17](sssql17-md.md)] and a float starting with [!INCLUDE[sql-server-2019](sssqlv15-md.md)] and in [!INCLUDE[ssSDSfull](sssdsfull-md.md)] managed instance. Default value is 25. The allowed range for *value* is from 1 through 100.
44
+
*value* is an integer up to [!INCLUDE[ssSQL17](sssql17-md.md)] and a float starting with [!INCLUDE[sql-server-2019](sssqlv15-md.md)] and in Azure SQL Managed Instance. Default value is 25. The allowed range for *value* is from 1 through 100.
45
45
46
46
> [!IMPORTANT]
47
47
> The amount specified only refers to query execution grant memory.
Copy file name to clipboardExpand all lines: docs/integration-services/connection-manager/ado-net-connection-manager.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
@@ -79,10 +79,10 @@ Create an ADO.NET data connection by using the **Connection Manager** dialog box
79
79
Select a connection, and then delete it by selecting **Delete**.
80
80
81
81
#### Managed identities for Azure resources authentication
82
-
When running SSIS packages on [Azure-SSIS integration runtime in Azure Data Factory](https://docs.microsoft.com/azure/data-factory/concepts-integration-runtime#azure-ssis-integration-runtime), you can use the [managed identity](https://docs.microsoft.com/azure/data-factory/connector-azure-sql-database#managed-identity) associated with your data factory for Azure SQL Database (or managed instance) authentication. The designated factory can access and copy data from or to your database by using this identity.
82
+
When running SSIS packages on [Azure-SSIS integration runtime in Azure Data Factory](https://docs.microsoft.com/azure/data-factory/concepts-integration-runtime#azure-ssis-integration-runtime), you can use the [managed identity](https://docs.microsoft.com/azure/data-factory/connector-azure-sql-database#managed-identity) associated with your data factory for Azure SQL Database or Azure SQL Managed Instance authentication. The designated factory can access and copy data from or to your database by using this identity.
83
83
84
84
> [!NOTE]
85
-
> When you use Azure Active Directory (Azure AD) authentication (including managed identity authentication) to connect to Azure SQL Database (or managed instance), you might encounter a problem related to package execution failure or unexpected behavior change. For more information, see [Azure AD features and limitations](https://docs.microsoft.com/azure/sql-database/sql-database-aad-authentication#azure-ad-features-and-limitations).
85
+
> When you use Azure Active Directory (Azure AD) authentication (including managed identity authentication) to connect to Azure SQL Database or Azure SQL Managed Instance, you might encounter a problem related to package execution failure or unexpected behavior change. For more information, see [Azure AD features and limitations](https://docs.microsoft.com/azure/sql-database/sql-database-aad-authentication#azure-ad-features-and-limitations).
86
86
87
87
To use managed identity authentication for Azure SQL Database, follow these steps to configure your database:
Copy file name to clipboardExpand all lines: docs/integration-services/connection-manager/ole-db-connection-manager.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
@@ -81,10 +81,10 @@ Use the **Configure OLE DB Connection Manager** dialog box to add a connection t
81
81
Select a data connection, and then delete it by selecting **Delete**.
82
82
83
83
#### Managed identities for Azure resources authentication
84
-
When running SSIS packages on [Azure-SSIS integration runtime in Azure Data Factory](https://docs.microsoft.com/azure/data-factory/concepts-integration-runtime#azure-ssis-integration-runtime), use the [managed identity](https://docs.microsoft.com/azure/data-factory/connector-azure-sql-database#managed-identity) associated with your data factory for Azure SQL Database (or managed instance) authentication. The designated factory can access and copy data from or to your database by using this identity.
84
+
When running SSIS packages on [Azure-SSIS integration runtime in Azure Data Factory](https://docs.microsoft.com/azure/data-factory/concepts-integration-runtime#azure-ssis-integration-runtime), use the [managed identity](https://docs.microsoft.com/azure/data-factory/connector-azure-sql-database#managed-identity) associated with your data factory for Azure SQL Database or Managed Instance authentication. The designated factory can access and copy data from or to your database by using this identity.
85
85
86
86
> [!NOTE]
87
-
> When you use Azure Active Directory (Azure AD) authentication (including managed identity authentication) to connect to Azure SQL Database (or managed instance), you might encounter a problem related to package execution failure or unexpected behavior change. For more information, see [Azure AD features and limitations](https://docs.microsoft.com/azure/sql-database/sql-database-aad-authentication#azure-ad-features-and-limitations).
87
+
> When you use Azure Active Directory (Azure AD) authentication (including managed identity authentication) to connect to Azure SQL Database or Managed Instance, you might encounter a problem related to package execution failure or unexpected behavior change. For more information, see [Azure AD features and limitations](https://docs.microsoft.com/azure/sql-database/sql-database-aad-authentication#azure-ad-features-and-limitations).
88
88
89
89
To use managed identity authentication for Azure SQL Database, follow these steps to configure your database:
Copy file name to clipboardExpand all lines: docs/relational-databases/backup-restore/copy-only-backups-sql-server.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ A *copy-only backup* is a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.m
39
39
Copy-only backups are recorded in the **is_copy_only** column of the [backupset](../../relational-databases/system-tables/backupset-transact-sql.md) table.
40
40
41
41
> [!IMPORTANT]
42
-
> In Azure SQL managed instance copy-only backup cannot be created for a database encrypted with [service-managed Transparent Data Encryption (TDE)](https://docs.microsoft.com/azure/sql-database/transparent-data-encryption-azure-sql?tabs=azure-portal#service-managed-transparent-data-encryption). Service-managed TDE uses internal key for encryption of data, and that key cannot be exported, so you could not restore the backup anywhere else. Consider using [customer-managed TDE](https://docs.microsoft.com/azure/sql-database/transparent-data-encryption-byok-azure-sql) instead to be able to create copy-only backups of encrypted databases, but make sure to have encryption key available for later restore.
42
+
> In Azure SQL Managed Instance copy-only backup cannot be created for a database encrypted with [service-managed Transparent Data Encryption (TDE)](https://docs.microsoft.com/azure/sql-database/transparent-data-encryption-azure-sql?tabs=azure-portal#service-managed-transparent-data-encryption). Service-managed TDE uses internal key for encryption of data, and that key cannot be exported, so you could not restore the backup anywhere else. Consider using [customer-managed TDE](https://docs.microsoft.com/azure/sql-database/transparent-data-encryption-byok-azure-sql) instead to be able to create copy-only backups of encrypted databases, but make sure to have encryption key available for later restore.
43
43
44
44
## To Create a Copy-Only Backup
45
45
You can create a copy-only backup by using [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)], [!INCLUDE[tsql](../../includes/tsql-md.md)], or PowerShell.
0 commit comments