Merge branch 'MicrosoftDocs:main' into 20230123-retire-latest-updates

Author: MikeRayMSFT

.openpublishing.redirection.json

@@ -52148,42 +52148,42 @@
     {
       "source_path": "docs/relational-databases/scripting/configure-intellisense-sql-server-management-studio.md",
       "redirect_url": "/sql/ssms/scripting/configure-intellisense-sql-server-management-studio",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/relational-databases/scripting/database-engine-query-editor-sql-server-management-studio.md",
       "redirect_url": "/sql/ssms/scripting/database-engine-query-editor-sql-server-management-studio",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/relational-databases/scripting/database-engine-scripting.md",
       "redirect_url": "/sql/ssms/scripting/database-engine-scripting",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/relational-databases/scripting/drag-and-drop-text.md",
       "redirect_url": "/sql/ssms/scripting/drag-and-drop-text",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/relational-databases/scripting/edit-a-breakpoint-location.md",
       "redirect_url": "/sql/ssms/scripting/edit-a-breakpoint-location",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/relational-databases/scripting/edit-sqlcmd-scripts-with-query-editor.md",
       "redirect_url": "/sql/ssms/scripting/edit-sqlcmd-scripts-with-query-editor",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/relational-databases/scripting/enable-disable-and-delete-breakpoints.md",
       "redirect_url": "/sql/ssms/scripting/enable-disable-and-delete-breakpoints",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/relational-databases/scripting/find-and-replace.md",
       "redirect_url": "/sql/ssms/scripting/find-and-replace",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/relational-databases/scripting/find-in-files.md",
@@ -59490,6 +59490,46 @@
       "redirect_url": "/sql/tools/distributed-replay/sql-server-distributed-replay",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/tools/sqlcmd-utility.md",
+      "redirect_url": "/sql/tools/sqlcmd/sqlcmd-utility",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/ssms/scripting/edit-sqlcmd-scripts-with-query-editor.md",
+      "redirect_url": "/sql/tools/sqlcmd/edit-sqlcmd-scripts-query-editor",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/ssms/scripting/sqlcmd-start-the-utility.md",
+      "redirect_url": "/sql/tools/sqlcmd/sqlcmd-start-utility",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/ssms/scripting/sqlcmd-connect-to-the-database-engine.md",
+      "redirect_url": "/sql/tools/sqlcmd/sqlcmd-connect-database-engine",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/ssms/scripting/sqlcmd-run-transact-sql-script-files.md",
+      "redirect_url": "/sql/tools/sqlcmd/sqlcmd-run-transact-sql-script-files",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/ssms/scripting/sqlcmd-use-the-utility.md",
+      "redirect_url": "/sql/tools/sqlcmd/sqlcmd-use-utility",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/ssms/scripting/sqlcmd-use-with-scripting-variables.md",
+      "redirect_url": "/sql/tools/sqlcmd/sqlcmd-use-scripting-variables",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/tools/go-sqlcmd-utility.md",
+      "redirect_url": "/sql/tools/sqlcmd/go-sqlcmd-utility",
+      "redirect_document_id": true
+    },
     {
       "source_path": "docs/ssms/scripting/transact-sql-debugger-quickwatch-dialog-box.md",
       "redirect_url": "/sql/ssms/scripting/transact-sql-debugger-information",

azure-sql/includes/azure-sql-gen4-hardware-retirement-sql-managed-instance.md

@@ -0,0 +1,15 @@
+---
+title: Inform customers of impending Gen4 hardware retirement and recommendations for Azure SQL Managed Instance.
+description: Inform customers of impending Gen4 hardware retirement and recommendations for Azure SQL Managed Instance.
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.date: 01/30/2023
+ms.topic: include
+---
+
+> [!IMPORTANT]
+> [Gen4 hardware is being retired](https://azure.microsoft.com/updates/gen-4-hardware-on-azure-sql-database-approaching-end-of-life-in-2020) and is not available for new deployments, as announced on December 18, 2019. Customers using Gen4 hardware for Azure SQL Database, elastic pools, or SQL Managed Instance should migrate to currently available hardware, such as standard-series (Gen5), **before March 31, 2023**.
+>
+> By March 31, 2023, existing Gen4 SQL managed instances will be migrated automatically to equivalent or better hardware. If upgraded automatically, managed instances may be upgraded to premium-series hardware, which will result in price increase in accordance with [pricing](https://azure.microsoft.com/pricing/details/azure-sql-managed-instance/single/#pricing). 
+>
+> Downtime caused by automatic migration will be minimal and similar to downtime during scaling operations within selected service tier. To avoid unplanned interruptions to workloads, migrate proactively at the time of your choice before March 31, 2023. For more information on Gen4 hardware retirement and migration to current hardware, see our [blog post on Gen4 retirement](https://aka.ms/AAh8l4v).

azure-sql/includes/azure-sql-gen4-hardware-retirement.md

@@ -1,15 +1,13 @@
 ---
 title: Inform customers of impending Gen4 hardware retirement and recommendations.
-description: Inform customers of impending Gen4 hardware retirement and recommendations. Should no longer be necessary after Jan 2023.
-author: WilliamDAssaf
+description: Inform customers of impending Gen4 hardware retirement and recommendations.
+author: WilliamDAssafMSFT
 ms.author: wiassaf
-ms.date: 06/13/2022
+ms.date: 01/30/2023
 ms.topic: include
 ---
 
 > [!IMPORTANT]
-> Gen4 hardware is being retired and is not available for new deployments, as [announced](https://azure.microsoft.com/updates/gen-4-hardware-on-azure-sql-database-approaching-end-of-life-in-2020) on December 18, 2019. Customers using Gen4 for Azure SQL Databases, elastic pools, or SQL managed instances should migrate to currently available hardware, such as standard-series (Gen5), before January 31, 2023.
+> [Gen4 hardware is being retired](https://azure.microsoft.com/updates/gen-4-hardware-on-azure-sql-database-approaching-end-of-life-in-2020) and is not available for new deployments, as announced on December 18, 2019. Customers using Gen4 hardware for Azure SQL Database, elastic pools, or SQL Managed Instance should migrate to currently available hardware, such as standard-series (Gen5), **before March 31, 2023**. Existing Gen4 databases, elastic pools, and SQL managed instances will be migrated automatically to equivalent standard-series (Gen5) hardware.
 >
-> For more information on Gen4 hardware retirement and migration to current hardware, see our [Blog post on Gen4 retirement](https://aka.ms/AAh8l4v). Existing Gen4 databases, elastic pools, and SQL managed instances will be migrated automatically to equivalent standard-series (Gen5) hardware.
->
-> Downtime caused by automatic migration will be minimal and similar to downtime during scaling operations within selected service tier. To avoid unplanned interruptions to workloads, migrate proactively at the time of your choice before January 31, 2023.
+> Downtime caused by automatic migration will be minimal and similar to downtime during scaling operations within selected service tier. To avoid unplanned interruptions to workloads, migrate proactively at the time of your choice before March 31, 2023. For more information on Gen4 hardware retirement and migration to current hardware, see our [blog post on Gen4 retirement](https://aka.ms/AAh8l4v). 

azure-sql/managed-instance/managed-instance-link-feature-overview.md

@@ -37,7 +37,9 @@ You can keep running the link for as long as you need it, for months and even ye
 
 ## Prerequisites
 
-To use the link feature, you'll need a supported Enterprise, Standard, or Developer edition of SQL Server running on Windows Server.
+The Managed Instance link is supported on both the General Purpose and Business Critical service tier of Azure SQL Managed Instance. 
+
+To use the link feature with SQL Server, you'll need a supported Enterprise, Standard, or Developer edition of SQL Server running on Windows Server.
 
 The following table lists the functionality of the link feature and the supported SQL Server versions:
 

azure-sql/managed-instance/resource-limits.md

@@ -215,7 +215,7 @@ If you need more instances in your current regions, send a support request to ex
 
 This section includes details on previously available hardware. Consider [moving your instance of SQL Managed Instance to the standard-series (Gen5)](../database/service-tiers-vcore.md) hardware to experience a wider range of vCore and storage scalability, accelerated networking, best IO performance, and minimal latency.
 
-[!INCLUDE[azure-sql-gen4-hardware-retirement](../includes/azure-sql-gen4-hardware-retirement.md)]
+[!INCLUDE[azure-sql-gen4-hardware-retirement-sql-managed-instance](../includes/azure-sql-gen4-hardware-retirement-sql-managed-instance.md)]
 
 ### Hardware characteristics
 
@@ -229,7 +229,7 @@ This section includes details on previously available hardware. Consider [moving
 
 ### In-memory OLTP available space
 
-[!INCLUDE[azure-sql-gen4-hardware-retirement](../includes/azure-sql-gen4-hardware-retirement.md)]
+[!INCLUDE[azure-sql-gen4-hardware-retirement-sql-managed-instance](../includes/azure-sql-gen4-hardware-retirement-sql-managed-instance.md)]
 
 The amount of In-memory OLTP space in [Business Critical](../database/service-tier-business-critical.md) service tier depends on the number of vCores and hardware configuration. The following table lists limits of memory that can be used for In-memory OLTP objects.
 
@@ -242,7 +242,7 @@ The amount of In-memory OLTP space in [Business Critical](../database/service-ti
 
 ### Service tier characteristics
 
-[!INCLUDE[azure-sql-gen4-hardware-retirement](../includes/azure-sql-gen4-hardware-retirement.md)]
+[!INCLUDE[azure-sql-gen4-hardware-retirement-sql-managed-instance](../includes/azure-sql-gen4-hardware-retirement-sql-managed-instance.md)]
 
 | **Feature** | **General Purpose** | **Business Critical** |
 | --- | --- | --- |

azure-sql/managed-instance/service-tiers-managed-instance-vcore.md

@@ -124,7 +124,7 @@ When specifying hardware parameter in templates or scripts, hardware is provided
 
 #### <a id="gen4gen5-1"></a> Gen4
 
-[!INCLUDE[azure-sql-gen4-hardware-retirement](../includes/azure-sql-gen4-hardware-retirement.md)]
+[!INCLUDE[azure-sql-gen4-hardware-retirement-sql-managed-instance](../includes/azure-sql-gen4-hardware-retirement-sql-managed-instance.md)]
 
 #### Standard-series (Gen5) and premium-series
 

azure-sql/managed-instance/vnet-subnet-move-instance.md

@@ -91,7 +91,7 @@ To learn more about configuring the network for auto-failover groups, review [En
 
 Instances running on Gen4 hardware must be upgraded to newer hardware since Gen4 is being retired. Upgrading hardware and moving to another subnet can be performed in one operation.
 
-[!INCLUDE[azure-sql-gen4-hardware-retirement](../includes/azure-sql-gen4-hardware-retirement.md)]
+[!INCLUDE[azure-sql-gen4-hardware-retirement-sql-managed-instance](../includes/azure-sql-gen4-hardware-retirement-sql-managed-instance.md)]
 
 ## Operation steps
 

azure-sql/virtual-machines/windows/availability-group-manually-configure-tutorial-single-subnet.md

@@ -42,6 +42,7 @@ The following table summarizes the prerequisites that you need before you can co
 |:::image type="icon" source="./media/availability-group-manually-configure-tutorial-single-subnet/square.png" border="false":::   **Firewall ports open** | - SQL Server: **1433** for a default instance <br/> - Database mirroring endpoint: **5022** or any available port <br/> - Load balancer IP address health probe for an availability group: **59999** or any available port <br/> - Load balancer IP address health probe for cluster core: **58888** or any available port |
 |:::image type="icon" source="./media/availability-group-manually-configure-tutorial-single-subnet/square.png" border="false":::   **Failover clustering** | Required for both SQL Server instances |
 |:::image type="icon" source="./media/availability-group-manually-configure-tutorial-single-subnet/square.png" border="false":::   **Installation domain account** | - Local administrator on each SQL Server instance <br/> - Member of the **sysadmin** fixed server role for each SQL Server instance  |
+|:::image type="icon" source="./media/availability-group-manually-configure-tutorial-single-subnet/square.png" border="false":::   **Network Security Groups (NSGs)** | If the environment is using [Network security groups](/azure/virtual-network/network-security-groups-overview), ensure that the current configuration **allows Network traffic** through ports described in [Configure the firewall](availability-group-manually-configure-prerequisites-tutorial-single-subnet.md#endpoint-firewall). |
 
 ## <a name="create-the-cluster"></a> Create the cluster
 

docs/azure-data-studio/download-azure-data-studio.md

@@ -4,7 +4,7 @@ description: Download and install Azure Data Studio for Windows, macOS, or Linux
 author: erinstellato-ms
 ms.author: erinstellato
 ms.reviewer: maghan, randolphwest
-ms.date: 01/25/2023
+ms.date: 01/30/2023
 ms.service: azure-data-studio
 ms.topic: overview
 ms.custom:
@@ -25,10 +25,10 @@ For more information about Azure Data Studio, visit [What is Azure Data Studio?]
 
 ## Download Azure Data Studio
 
-Azure Data Studio 1.41.0 is the latest general availability (GA) version.
+Azure Data Studio 1.41.1 is the latest general availability (GA) version.
 
-- Release number: 1.41.0
-- Release date: January 25, 2023
+- Release number: 1.41.1
+- Release date: January 30, 2023
 
 | Platform | Type | Download |
 | --- | --- | --- |

docs/azure-data-studio/faq.yml

@@ -18,7 +18,7 @@ sections:
     questions:
       - question: What is Azure Data Studio?
         answer: |
-          [Azure Data Studio](what-is-azure-data-studio.md) is an open source, cross-platform desktop environment for data professionals using the Azure Data family of on-premises and cloud data platforms on Windows, macOS, and Linux. Previously released under the preview name SQL Operations Studio, Azure Data Studio offers a modern editor experience with lightning fast IntelliSense, code snippets, source control integration, and an integrated terminal. it's engineered with the data platform user in mind, with built-in charting of query result sets and customizable dashboards.
+          [Azure Data Studio](what-is-azure-data-studio.md) is an open source, cross-platform desktop environment for data professionals using the Azure Data family of on-premises and cloud data platforms on Windows, macOS, and Linux. Previously released under the preview name SQL Operations Studio, Azure Data Studio offers a modern editor experience with lightning fast IntelliSense, code snippets, source control integration, and an integrated terminal. It's engineered with the data platform user in mind, with built-in charting of query result sets and customizable dashboards.
           
           Research has shown that users spend an order of magnitude more time working on query editing than on any other task with SQL Server Management Studio. For that reason, Azure Data Studio has been designed to focus deeply on the functionality that is used the most, with additional experiences made available as optional extensions into the product. Every user is allowed to customize their environment to the workflows that they use most often.