Merge pull request #30310 from rwestMSFT/rw-0405-refresh-linux-2022

[WIP] Old Linux article refresh (articles older than 2023)

Author: v-shils

docs/linux/includes/change-docker-password.md

@@ -8,7 +8,7 @@ ms.topic: include
 ms.custom:
   - linux-related-content
 ---
-The **SA** account is a system administrator on the SQL Server instance that's created during setup. After you create your SQL Server container, the `MSSQL_SA_PASSWORD` environment variable you specified is discoverable by running `echo $MSSQL_SA_PASSWORD` in the container. For security purposes, change your SA password:
+The `SA` account is a system administrator on the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance that's created during setup. After you create your [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] container, the `MSSQL_SA_PASSWORD` environment variable you specified is discoverable by running `echo $MSSQL_SA_PASSWORD` in the container. For security purposes, change your SA password:
 
 1. Choose a strong password to use for the SA user.
 

docs/linux/includes/cluster-availability-group-create-post.md

@@ -10,7 +10,7 @@ ms.custom:
 ---
 ## Add a database to the availability group
 
-Ensure that the database you add to the availability group is in the full recovery model and has a valid log backup. If this is a test database or a newly created database, take a database backup. On the primary SQL Server, run the following Transact-SQL script to create and back up a database called `db1`:
+Ensure that the database you add to the availability group is in the full recovery model and has a valid log backup. If this is a test database or a newly created database, take a database backup. On the primary [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], run the following Transact-SQL script to create and back up a database called `db1`:
 
 ```sql
 CREATE DATABASE [db1];
@@ -19,15 +19,15 @@ BACKUP DATABASE [db1]
    TO DISK = N'/var/opt/mssql/data/db1.bak';
 ```
 
-On the primary SQL Server replica, run the following Transact-SQL script to add a database called `db1` to an availability group called `ag1`:
+On the primary [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] replica, run the following Transact-SQL script to add a database called `db1` to an availability group called `ag1`:
 
 ```sql
 ALTER AVAILABILITY GROUP [ag1] ADD DATABASE [db1];
 ```
 
 ### Verify that the database is created on the secondary servers
 
-On each secondary SQL Server replica, run the following query to see if the `db1` database was created and is synchronized:
+On each secondary [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] replica, run the following query to see if the `db1` database was created and is synchronized:
 
 ```sql
 SELECT * FROM sys.databases WHERE name = 'db1';

docs/linux/includes/cluster-availability-group-create-prereq.md

@@ -1,7 +1,7 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 09/15/2022
+ms.date: 07/15/2024
 ms.service: sql
 ms.subservice: linux
 ms.topic: include
@@ -13,17 +13,15 @@ ms.custom:
 Before you create the availability group, you need to:
 
 - Set your environment so that all the servers that will host availability replicas can communicate.
-- Install SQL Server.
+- Install [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)].
 
-> [!NOTE]
->  
-> On Linux, you must create an availability group before you add it as a cluster resource to be managed by the cluster. This document provides an example that creates the availability group. For distribution-specific instructions to create the cluster and add the availability group as a cluster resource, see the links under "Next steps."
+On Linux, you must create an availability group before you add it as a cluster resource to be managed by the cluster. This document provides an example that creates the availability group.
 
 1. Update the computer name for each host.
 
-   Each SQL Server name must be:
+   Each [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance name must be:
 
-   - 15 characters or less.
+   - 15 characters or fewer.
    - Unique within the network.
 
    To set the computer name, edit `/etc/hostname`. The following script lets you edit `/etc/hostname` with **vi**:
@@ -32,11 +30,10 @@ Before you create the availability group, you need to:
    sudo vi /etc/hostname
    ```
 
-2. Configure the hosts file.
+1. Configure the hosts file.
 
-    > [!NOTE]
-    >  
-    > If hostnames are registered with their IP address in the DNS server, you don't need to do the following steps. Validate that all the nodes intended to be part of the availability group configuration can communicate with each other. (A ping to the hostname should reply with the corresponding IP address.) Also, make sure that the `/etc/hosts` file doesn't contain a record that maps the localhost IP address 127.0.0.1 with the hostname of the node.
+   > [!NOTE]  
+   > If hostnames are registered with their IP address in the DNS server, you don't need to do the following steps. Validate that all the nodes intended to be part of the availability group configuration can communicate with each other. (A ping to the hostname should reply with the corresponding IP address.) Also, make sure that the `/etc/hosts` file doesn't contain a record that maps the localhost IP address 127.0.0.1 with the hostname of the node.
 
    The hosts file on every server contains the IP addresses and names of all servers that will participate in the availability group.
 
@@ -54,7 +51,7 @@ Before you create the availability group, you need to:
 
    The following example shows `/etc/hosts` on `node1` with additions for `node1`, `node2`, and `node3`. In this sample, `node1` refers to the server that hosts the primary replica, and `node2` and `node3` refer to servers that host the secondary replicas.
 
-   ```
+   ```output
    127.0.0.1    localhost localhost4 localhost4.localdomain4
    ::1          localhost localhost6 localhost6.localdomain6
    10.128.18.12 node1
@@ -64,56 +61,56 @@ Before you create the availability group, you need to:
 
 ### Install SQL Server
 
-Install SQL Server. The following links point to SQL Server installation instructions for various distributions:
+Install [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)]. The following links point to [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] installation instructions for various distributions:
 
-- [Red Hat Enterprise Linux](../quickstart-install-connect-red-hat.md)
-- [SUSE Linux Enterprise Server](../quickstart-install-connect-suse.md)
-- [Ubuntu](../quickstart-install-connect-ubuntu.md)
+- [Quickstart: Install SQL Server and create a database on Red Hat](../quickstart-install-connect-red-hat.md)
+- [Quickstart: Install SQL Server and create a database on SUSE Linux Enterprise Server](../quickstart-install-connect-suse.md)
+- [Quickstart: Install SQL Server and create a database on Ubuntu](../quickstart-install-connect-ubuntu.md)
 
 ## Enable Always On availability groups
 
-Enable Always On availability groups for each node that hosts a SQL Server instance, and then restart `mssql-server`. Run the following script:
+Enable Always On availability groups for each node that hosts a [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance, and then restart `mssql-server`. Run the following script:
 
 ```bash
 sudo /opt/mssql/bin/mssql-conf set hadr.hadrenabled 1
 sudo systemctl restart mssql-server
 ```
 
-## Enable an AlwaysOn_health event session
+## Enable an AlwaysOn_health Event session
 
-You can optionally enable extended events (XE) to help with root-cause diagnosis when you troubleshoot an availability group. Run the following command on each instance of SQL Server:
+You can optionally enable Extended Events (XE) to help with root-cause diagnosis when you troubleshoot an availability group. Run the following command on each instance of [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)]:
 
 ```SQL
-ALTER EVENT SESSION AlwaysOn_health ON SERVER WITH (STARTUP_STATE=ON);
+ALTER EVENT SESSION AlwaysOn_health ON SERVER WITH (STARTUP_STATE = ON);
 GO
 ```
 
-For more information about this XE session, see [Configure extended events for Always On availability groups](../../database-engine/availability-groups/windows/always-on-extended-events.md).
+For more information about this XE session, see [Configure Extended Events for availability groups](../../database-engine/availability-groups/windows/always-on-extended-events.md).
 
 ## Create a certificate
 
-The SQL Server service on Linux uses certificates to authenticate communication between the mirroring endpoints.
+The [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] service on Linux uses certificates to authenticate communication between the mirroring endpoints.
 
-The following Transact-SQL script creates a master key and a certificate. It then backs up the certificate and secures the file with a private key. Update the script with strong passwords. Connect to the primary SQL Server instance. To create the certificate, run the following Transact-SQL script:
+The following Transact-SQL script creates a master key and a certificate. It then backs up the certificate and secures the file with a private key. Update the script with strong passwords. Connect to the primary [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instance. To create the certificate, run the following Transact-SQL script:
 
 ```SQL
-CREATE MASTER KEY ENCRYPTION BY PASSWORD = '**<Master_Key_Password>**';
+CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<Master_Key_Password>';
 CREATE CERTIFICATE dbm_certificate WITH SUBJECT = 'dbm';
 BACKUP CERTIFICATE dbm_certificate
-   TO FILE = '/var/opt/mssql/data/dbm_certificate.cer'
-   WITH PRIVATE KEY (
-           FILE = '/var/opt/mssql/data/dbm_certificate.pvk',
-           ENCRYPTION BY PASSWORD = '**<Private_Key_Password>**'
-        );
+    TO FILE = '/var/opt/mssql/data/dbm_certificate.cer'
+    WITH PRIVATE KEY (
+        FILE = '/var/opt/mssql/data/dbm_certificate.pvk',
+        ENCRYPTION BY PASSWORD = '<Private_Key_Password>'
+    );
 ```
 
-At this point, your primary SQL Server replica has a certificate at `/var/opt/mssql/data/dbm_certificate.cer` and a private key at `var/opt/mssql/data/dbm_certificate.pvk`. Copy these two files to the same location on all servers that will host availability replicas. Use the mssql user, or give permission to the mssql user to access these files.
+At this point, your primary [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] replica has a certificate at `/var/opt/mssql/data/dbm_certificate.cer` and a private key at `var/opt/mssql/data/dbm_certificate.pvk`. Copy these two files to the same location on all servers that will host availability replicas. Use the mssql user, or give permission to the mssql user to access these files.
 
-For example, on the source server, the following command copies the files to the target machine. Replace the `**<node2>**` values with the names of the SQL Server instances that will host the replicas.
+For example, on the source server, the following command copies the files to the target machine. Replace the `<node2>` values with the names of the [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instances that will host the replicas.
 
 ```bash
 cd /var/opt/mssql/data
-scp dbm_certificate.* root@**<node2>**:/var/opt/mssql/data/
+scp dbm_certificate.* root@<node2>:/var/opt/mssql/data/
 ```
 
 On each target server, give permission to the mssql user to access the certificate.
@@ -125,58 +122,57 @@ chown mssql:mssql dbm_certificate.*
 
 ## Create the certificate on secondary servers
 
-The following Transact-SQL script creates a master key and a certificate from the backup that you created on the primary SQL Server replica. Update the script with strong passwords. The decryption password is the same password that you used to create the .pvk file in a previous step. To create the certificate, run the following script on all secondary servers:
+The following Transact-SQL script creates a master key and a certificate from the backup that you created on the primary [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] replica. Update the script with strong passwords. The decryption password is the same password that you used to create the .pvk file in a previous step. To create the certificate, run the following script on all secondary servers:
 
 ```SQL
-CREATE MASTER KEY ENCRYPTION BY PASSWORD = '**<Master_Key_Password>**';
+CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<Master_Key_Password>';
 CREATE CERTIFICATE dbm_certificate
     FROM FILE = '/var/opt/mssql/data/dbm_certificate.cer'
     WITH PRIVATE KEY (
-           FILE = '/var/opt/mssql/data/dbm_certificate.pvk',
-           DECRYPTION BY PASSWORD = '**<Private_Key_Password>**'
-        );
+        FILE = '/var/opt/mssql/data/dbm_certificate.pvk',
+        DECRYPTION BY PASSWORD = '<Private_Key_Password>'
+    );
 ```
 
 ## Create the database mirroring endpoints on all replicas
 
-Database mirroring endpoints use the Transmission Control Protocol (TCP) to send and receive messages between the server instances that participate in database mirroring sessions or host availability replicas. The database mirroring endpoint listens on a unique TCP port number.
+Database mirroring endpoints use the Transmission Control Protocol (TCP) to send and receive messages between the server instances that participate in database mirroring sessions, or host availability replicas. The database mirroring endpoint listens on a unique TCP port number.
 
-The following Transact-SQL script creates a listening endpoint named `Hadr_endpoint` for the availability group. It starts the endpoint and gives connection permission to the certificate that you created. Before you run the script, replace the values between `**< ... >**`. Optionally you can include an IP address `LISTENER_IP = (0.0.0.0)`. The listener IP address must be an IPv4 address. You can also use `0.0.0.0`.
+The following Transact-SQL script creates a listening endpoint named `Hadr_endpoint` for the availability group. It starts the endpoint and gives connection permission to the certificate that you created. Before you run the script, replace the values between `< ... >`. Optionally you can include an IP address `LISTENER_IP = (0.0.0.0)`. The listener IP address must be an IPv4 address. You can also use `0.0.0.0`.
 
-Update the following Transact-SQL script for your environment on all SQL Server instances:
+Update the following Transact-SQL script for your environment on all [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] instances:
 
 ```SQL
 CREATE ENDPOINT [Hadr_endpoint]
-    AS TCP (LISTENER_PORT = **<5022>**)
+    AS TCP (LISTENER_PORT = 5022)
     FOR DATABASE_MIRRORING (
         ROLE = ALL,
         AUTHENTICATION = CERTIFICATE dbm_certificate,
         ENCRYPTION = REQUIRED ALGORITHM AES
-        );
+    );
 
 ALTER ENDPOINT [Hadr_endpoint] STATE = STARTED;
 ```
 
-> [!NOTE]
+> [!NOTE]  
 >  
-> If you use SQL Server Express Edition on one node to host a configuration-only replica, the only valid value for `ROLE` is `WITNESS`. Run the following script on SQL Server Express Edition:
+> If you use [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Express edition on one node to host a configuration-only replica, the only valid value for `ROLE` is `WITNESS`. Run the following script on [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] Express edition:
 
 ```SQL
 CREATE ENDPOINT [Hadr_endpoint]
-    AS TCP (LISTENER_PORT = **<5022>**)
+    AS TCP (LISTENER_PORT = 5022)
     FOR DATABASE_MIRRORING (
         ROLE = WITNESS,
         AUTHENTICATION = CERTIFICATE dbm_certificate,
         ENCRYPTION = REQUIRED ALGORITHM AES
-        );
+    );
 
 ALTER ENDPOINT [Hadr_endpoint] STATE = STARTED;
 ```
 
 The TCP port on the firewall must be open for the listener port.
 
-> [!IMPORTANT]
->  
-> For the SQL Server 2017 release, the only authentication method supported for the database mirroring endpoint is `CERTIFICATE`. The `WINDOWS` option will be enabled in a future release.
+> [!IMPORTANT]  
+> For [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)], the only authentication method supported for the database mirroring endpoint is `CERTIFICATE`. The `WINDOWS` option isn't available.
 
 For more information, see [The database mirroring endpoint (SQL Server)](../../database-engine/database-mirroring/the-database-mirroring-endpoint-sql-server.md).

docs/linux/includes/cluster-pacemaker-concepts.md

@@ -70,7 +70,7 @@ The following tables describe the outcome of an outage for primary or secondary
 | `REQUIRED_COPIES_TO_COMMIT = 0` | User has to issue a manual `FAILOVER`.<br />Might have data loss.<br />New primary is R/W | Primary is R/W, running exposed to data loss. |
 | `REQUIRED_COPIES_TO_COMMIT = 1` <sup>1</sup> | Cluster automatically issues `FAILOVER`<br />No data loss.<br />New primary rejects all connections until former primary recovers and joins availability group as secondary. | Primary rejects all connections until secondary recovers. |
 
-<sup>1</sup> SQL Server resource agent for Pacemaker default behavior.
+<sup>1</sup> [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] resource agent for Pacemaker default behavior.
 
 ### Availability group - three sync replicas
 
@@ -79,4 +79,4 @@ The following tables describe the outcome of an outage for primary or secondary
 | `REQUIRED_COPIES_TO_COMMIT = 0` | User has to issue a manual `FAILOVER`.<br />Might have data loss.<br />New primary is R/W | Primary is R/W |
 | `REQUIRED_COPIES_TO_COMMIT = 1` <sup>1</sup> | Cluster automatically issues `FAILOVER`.<br />No data loss.<br />New primary is RW | Primary is R/W |
 
-<sup>1</sup> SQL Server resource agent for Pacemaker default behavior.
+<sup>1</sup> [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] resource agent for Pacemaker default behavior.

docs/linux/includes/cluster-pacemaker-configure-rhel.md

@@ -1,7 +1,7 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 09/15/2022
+ms.date: 07/15/2024
 ms.service: sql
 ms.subservice: linux
 ms.topic: include
@@ -15,10 +15,10 @@ ms.custom:
    sudo firewall-cmd --reload
    ```
 
-   > If the firewall doesn't have a built-in high-availability configuration, open the following ports for Pacemaker.
-   >
-   > * TCP: Ports 2224, 3121, 21064
-   > * UDP: Port 5405
+   If the firewall doesn't have a built-in high-availability configuration, open the following ports for Pacemaker.
+
+   - TCP: Ports 2224, 3121, 21064
+   - UDP: Port 5405
 
 1. Install Pacemaker packages on all nodes.
 
@@ -51,9 +51,9 @@ ms.custom:
    sudo pcs cluster enable --all
    ```
 
-   **RHEL8**
+   **RHEL 8**
 
-   For RHEL 8, you will need to authenticate the nodes separately. Manually enter in the Username and Password for hacluster when prompted.
+   For RHEL 8, you need to authenticate the nodes separately. Manually enter in the Username and Password for hacluster when prompted.
 
    ```bash
    sudo pcs host auth <node1> <node2> <node3>
@@ -65,7 +65,7 @@ ms.custom:
    > [!NOTE]  
    > If you previously configured a cluster on the same nodes, you need to use `--force` option when running `pcs cluster setup`. This option is equivalent to running `pcs cluster destroy`. To re-enable Pacemaker, run `sudo systemctl enable pacemaker`.
 
-1. Install SQL Server resource agent for SQL Server. Run the following commands on all nodes.
+1. Install [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] resource agent for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)]. Run the following commands on all nodes.
 
    ```bash
    sudo yum install mssql-server-ha