Merge pull request #34607 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

docs/includes/business-continuity/business-continuity.md

@@ -1,26 +1,27 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 11/23/2022
+ms.date: 07/03/2025
 ms.service: sql
-ms.custom: linux-related-content
 ms.topic: include
+ms.custom:
+  - linux-related-content
 ---
-This article provides an overview of business continuity solutions for high availability and disaster recovery in [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)], on Windows and Linux.
+This article provides an overview of business continuity solutions for high availability and disaster recovery in [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)], on Windows and Linux.
 
-One common task everyone deploying [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] has to account for is making sure that all mission critical [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] instances and the databases within them are available when the business and end users need them, whether that is 9 to 5 or around the clock. The goal is to keep the business up and running with minimal or no interruption. This concept is also known as *business continuity*.
+One common task everyone deploying [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] has to account for is making sure that all mission critical [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] instances and the databases within them are available when the business and end users need them, whether that is 9 to 5 or around the clock. The goal is to keep the business up and running with minimal or no interruption. This concept is also known as *business continuity*.
 
-[!INCLUDE[sssql17-md](../sssql17-md.md)] introduced many new features or enhancements to existing ones, some of which are for availability. The biggest addition to [!INCLUDE[sssql17-md](../sssql17-md.md)] was support for [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] on Linux distributions. For a full list of the new features in [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)], see the following articles:
+[!INCLUDE [sssql17-md](../sssql17-md.md)] introduced many new features or enhancements to existing ones, some of which are for availability. The biggest addition to [!INCLUDE [sssql17-md](../sssql17-md.md)] was support for [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] on Linux distributions. For a full list of the new features in [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)], see the following articles:
 
 - [What's new in SQL Server 2017](../../sql-server/what-s-new-in-sql-server-2017.md)
 - [What's new for SQL Server 2017 on Linux](../../linux/sql-server-linux-whats-new.md)
 - [What's new in SQL Server 2019](../../sql-server/what-s-new-in-sql-server-2019.md)
 - [What's new for SQL Server 2019 on Linux](../../linux/sql-server-linux-whats-new-2019.md)
 - [What's new in SQL Server 2022](../../sql-server/what-s-new-in-sql-server-2022.md)
 
-This article is focused on covering the availability scenarios in [!INCLUDE[sssql17-md](../sssql17-md.md)] and later versions, as well as the new and enhanced availability features. The scenarios include hybrid ones that will be able to span [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] deployments on both Windows Server and Linux, and ones that can increase the number of readable copies of a database.
+This article is focused on covering the availability scenarios in [!INCLUDE [sssql17-md](../sssql17-md.md)] and later versions, as well as the new and enhanced availability features. The scenarios include hybrid ones that will be able to span [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] deployments on both Windows Server and Linux, and ones that can increase the number of readable copies of a database.
 
-While this article doesn't cover availability options external to [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)], such as those provided by virtualization, everything discussed here applies to [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] installations inside a guest virtual machine whether in the public cloud or hosted by an on-premises hypervisor server.
+While this article doesn't cover availability options external to [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)], such as those provided by virtualization, everything discussed here applies to [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] installations inside a guest virtual machine whether in the public cloud or hosted by an on-premises hypervisor server.
 
 ## SQL Server scenarios using the availability features
 
@@ -31,34 +32,34 @@ Always On availability groups, Always On failover cluster instances, and log shi
 - Migrations and upgrades
 - Scaling out readable copies of one or more databases
 
-The following sections discuss the relevant features that can be used for that particular scenario. The one feature not covered is [SQL Server replication](../../relational-databases/replication/sql-server-replication.md). While not officially designated as an availability feature under the Always On umbrella, [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] replication is often used for making data redundant in certain scenarios. Merge replication isn't supported for [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] on Linux. For more information, see [SQL Server Replication on Linux](../../linux/sql-server-linux-replication.md).
+The following sections discuss the relevant features that can be used for that particular scenario. The one feature not covered is [SQL Server replication](../../relational-databases/replication/sql-server-replication.md). While not officially designated as an availability feature under the Always On umbrella, [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] replication is often used for making data redundant in certain scenarios. Merge replication isn't supported for [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] on Linux. For more information, see [SQL Server replication on Linux](../../linux/sql-server-linux-replication.md).
 
 > [!IMPORTANT]  
-> The [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] availability features do not replace the requirement to have a robust, well tested backup and restore strategy, the most fundamental building block of any availability solution.
+> The [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] availability features don't replace the requirement to have a robust, well tested backup and restore strategy, the most fundamental building block of any availability solution.
 
-[!INCLUDE[sql-server-business-continuity-high-availability](high-availability.md)]
+[!INCLUDE [sql-server-business-continuity-high-availability](high-availability.md)]
 
-[!INCLUDE[sql-server-business-continuity-migrations](migrations.md)]
+[!INCLUDE [sql-server-business-continuity-migrations](migrations.md)]
 
 ## Cross-platform and Linux distribution interoperability
 
-With [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] now supported on both Windows Server and Linux, this section covers the scenarios of how they can work together for availability in addition to other purposes, and the story for solutions that will incorporate more than one Linux distribution.
+With [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] now supported on both Windows Server and Linux, this section covers the scenarios of how they can work together for availability in addition to other purposes, and the story for solutions that will incorporate more than one Linux distribution.
 
 > [!NOTE]  
 > There are no scenarios where a WSFC-based FCI or AG will work with a Linux-based FCI or AG directly. A WSFC can't be extended by a Pacemaker node and vice versa.
 
 ## Distributed availability groups
 
-Distributed AGs are designed to span AG configurations, whether those two underlying clusters underneath the AGs are two different WSFCs, Linux distributions, or one on a WSFC and the other on Linux. A distributed AG will be the primary method of having a cross platform solution. A distributed AG is also the primary solution for migrations such as converting from a Windows Server-based [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] infrastructure to a Linux-based one if that is what your company wants to do. As noted above, AGs, and especially distributed AGs, would minimize the time that an application would be unavailable for use. An example of a distributed AG that spans a WSFC and Pacemaker is shown below.
+Distributed AGs are designed to span AG configurations, whether those two underlying clusters underneath the AGs are two different WSFCs, Linux distributions, or one on a WSFC and the other on Linux. A distributed AG will be the primary method of having a cross platform solution. A distributed AG is also the primary solution for migrations such as converting from a Windows Server-based [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] infrastructure to a Linux-based one if that is what your company wants to do. As noted above, AGs, and especially distributed AGs, would minimize the time that an application would be unavailable for use. An example of a distributed AG that spans a WSFC and Pacemaker is shown below.
 
 :::image type="content" source="media/business-continuity/distributed-availability-group-span.png" alt-text="Diagram showing a distributed availability group that spans a WSFC and Pacemaker.":::
 
 If an AG is configured with a cluster type of None, it can span Windows Server and Linux, as well as multiple Linux distributions. Since this isn't a true high availability configuration, it shouldn't be used for mission critical deployments, but for read-scale or migration/upgrade scenarios.
 
 ## Log shipping
 
-Since log shipping is based on backup and restore, and there are no differences in the databases, file structures, etc., for [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] on Windows Server versus [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] on Linux. This means that log shipping can be configured between a Windows Server-based [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] installation and a Linux one, as well as between distributions of Linux. Everything else remains the same. The only caveat is that log shipping, just like an AG, can't work when the source is at a higher [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] major version against a target that is at a lower version of [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)].
+Since log shipping is based on backup and restore, and there are no differences in the databases, file structures, etc., for [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] on Windows Server versus [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] on Linux. This means that log shipping can be configured between a Windows Server-based [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] installation and a Linux one, as well as between distributions of Linux. Everything else remains the same. The only caveat is that log shipping, just like an AG, can't work when the source is at a higher [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] major version against a target that is at a lower version of [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)].
 
 ## Summary
 
-Instances and databases of [!INCLUDE[sssql17-md](../sssql17-md.md)] and later versions can be made highly available using the same features on both Windows Server and Linux. Besides standard availability scenarios of local high availability and disaster recovery, downtime associated with upgrades and migrations can be minimized with the availability features in [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)]. AGs can also provide additional copies of a database as part of the same architecture to scale out readable copies. Whether you're deploying a new solution or considering an upgrade, [!INCLUDE[ssnoversion-md](../ssnoversion-md.md)] has the availability and reliability you require.
+Instances and databases of [!INCLUDE [sssql17-md](../sssql17-md.md)] and later versions can be made highly available using the same features on both Windows Server and Linux. Besides standard availability scenarios of local high availability and disaster recovery, downtime associated with upgrades and migrations can be minimized with the availability features in [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)]. AGs can also provide additional copies of a database as part of the same architecture to scale out readable copies. Whether you're deploying a new solution or considering an upgrade, [!INCLUDE [ssnoversion-md](../ssnoversion-md.md)] has the availability and reliability you require.

docs/linux/includes/linux-forced-unit-access.md

@@ -1,14 +1,14 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 01/21/2025
+ms.date: 07/03/2025
 ms.service: sql
 ms.subservice: linux
 ms.topic: include
 ms.custom:
   - linux-related-content
 ---
-Certain versions of supported Linux distributions provide support for FUA I/O subsystem capability, which provides data durability. [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] uses the FUA capability to provide highly efficient and reliable I/O for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] workloads. For more information on FUA support by Linux distribution and its effect on [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], see [SQL Server On Linux: Forced Unit Access (FUA) Internals](https://techcommunity.microsoft.com/t5/sql-server-blog/sql-server-on-linux-forced-unit-access-fua-internals/ba-p/3199102).
+Certain versions of supported Linux distributions provide support for FUA I/O subsystem capability, which provides data durability. [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] uses the FUA capability to provide highly efficient and reliable I/O for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] workloads. For more information on FUA support by Linux distribution and its effect on [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], see [SQL Server On Linux: Forced Unit Access (FUA) Internals](https://techcommunity.microsoft.com/blog/sqlserver/sql-server-on-linux-forced-unit-access-fua-internals/3199102).
 
 SUSE Linux Enterprise Server 12 SP5, Red Hat Enterprise Linux 8.0, and Ubuntu 18.04 introduced support for FUA capability in the I/O subsystem. If you're using [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] CU 6 and later versions, you should use following configuration for high performing and efficient I/O implementation with FUA by [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)].
 

docs/linux/includes/roll-back-sql-server.md

@@ -1,7 +1,7 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 07/15/2024
+ms.date: 07/03/2025
 ms.service: sql
 ms.subservice: linux
 ms.topic: include
@@ -25,4 +25,4 @@ To roll back or downgrade [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-
    | **Ubuntu** | `sudo apt-get install mssql-server=<version_number>`<br />`sudo systemctl start mssql-server` |
 
 > [!NOTE]  
-> The only supported downgrade is if you downgrade to a release within the same major version, such as [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)].
+> The only supported downgrade is if you downgrade to a release within the same major version, such as [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)].

docs/linux/quickstart-install-connect-docker.md

@@ -4,7 +4,7 @@ description: This quickstart shows how to use Docker to run the SQL Server Linux
 author: amitkh-msft
 ms.author: amitkh
 ms.reviewer: vanto, randolphwest
-ms.date: 06/06/2025
+ms.date: 07/03/2025
 ms.service: sql
 ms.subservice: linux
 ms.topic: quickstart
@@ -110,28 +110,28 @@ The examples in this article use the `docker` command. However, most of these co
 <!--SQL Server 2017 on Linux-->
 ::: moniker range="=sql-server-linux-2017 || =sql-server-2017"
 
-- For more information on hardware requirements and processor support, see [SQL Server 2016 and 2017: Hardware and software requirements](../sql-server/install/hardware-and-software-requirements-for-installing-sql-server.md)
+- For more information on hardware requirements and processor support, see [Hardware and software requirements for SQL Server 2016 and SQL Server 2017](../sql-server/install/hardware-and-software-requirements-for-installing-sql-server.md)
 
 ::: moniker-end
 
 <!--SQL Server 2019 on Linux-->
 ::: moniker range="=sql-server-linux-ver15 || =sql-server-ver15"
 
-- For more information on hardware requirements and processor support, see [SQL Server 2019: Hardware and software requirements](../sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019.md)
+- For more information on hardware requirements and processor support, see [Hardware and software requirements for SQL Server 2019](../sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019.md)
 
 ::: moniker-end
 
 <!--SQL Server 2022 on Linux-->
 ::: moniker range="=sql-server-linux-ver16 || =sql-server-ver16"
 
-- For more information on hardware requirements and processor support, see [SQL Server 2022: Hardware and software requirements](../sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2022.md)
+- For more information on hardware requirements and processor support, see [Hardware and software requirements for SQL Server 2022](../sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2022.md)
 
 ::: moniker-end
 
 <!--SQL Server 2025 on Linux-->
 ::: moniker range=">=sql-server-linux-ver17 || >=sql-server-ver17"
 
-- For more information on hardware requirements and processor support, see [SQL Server 2025 Preview: Hardware and software requirements](../sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2025.md)
+- For more information on hardware requirements and processor support, see [Hardware and software requirements for SQL Server 2025 Preview](../sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2025.md)
 
 ::: moniker-end
 
@@ -1305,7 +1305,7 @@ The following steps use the [!INCLUDE [ssnoversion-md](../includes/ssnoversion-m
 <!--SQL Server 2017 on Linux-->
 ::: moniker range="=sql-server-linux-2017 || =sql-server-2017"
 
-1. Once inside the container, connect locally with **sqlcmd**, using its full path.
+2. Once inside the container, connect locally with **sqlcmd**, using its full path.
 
    ```bash
    /opt/mssql-tools/bin/sqlcmd -S localhost -U <userid> -P "<password>"
@@ -1324,7 +1324,7 @@ The following steps use the [!INCLUDE [ssnoversion-md](../includes/ssnoversion-m
 <!--SQL Server 2019 on Linux and later versions-->
 ::: moniker range=">=sql-server-linux-ver15 || >=sql-server-ver15"
 
-1. Once inside the container, connect locally with **sqlcmd**, using its full path.
+2. Once inside the container, connect locally with **sqlcmd**, using its full path.
 
    ```bash
    /opt/mssql-tools18/bin/sqlcmd -S localhost -U <userid> -P "<password>"
@@ -1340,7 +1340,7 @@ The following steps use the [!INCLUDE [ssnoversion-md](../includes/ssnoversion-m
 
 ::: moniker-end
 
-1. If successful, you should get to a **sqlcmd** command prompt: `1>`.
+3. If successful, you should get to a **sqlcmd** command prompt: `1>`.
 
 ## Create and query data
 
@@ -1523,7 +1523,7 @@ Other common tools to connect to [!INCLUDE [ssnoversion-md](../includes/ssnovers
 - [Use SQL Server Management Studio on Windows to manage SQL Server on Linux](sql-server-linux-manage-ssms.md)
 - [What is Azure Data Studio?](/azure-data-studio/what-is-azure-data-studio)
 - [mssql-cli (Preview)](https://github.com/dbcli/mssql-cli/blob/master/doc/usage_guide.md)
-- [Manage SQL Server on Linux with PowerShell Core](sql-server-linux-manage-powershell-core.md)
+- [Use PowerShell on Linux to manage SQL Server on Linux](sql-server-linux-manage-powershell-core.md)
 
 ## Remove your container