Merge pull request #28542 from rwestMSFT/rw-0926-recovery-model

[SCOPED] Recovery models are not recovery modes

Author: JamesJBarnett

azure-sql/managed-instance/managed-instance-link-preparation.md

@@ -52,7 +52,7 @@ To prepare your SQL Server instance, you need to validate that:
 - You're on the minimum supported version.
 - You've enabled the availability groups feature.
 - You've added the proper trace flags at startup.
-- Your databases are in full recovery mode and backed up.
+- Your databases are in the full recovery model and backed up.
 
 You'll need to restart SQL Server for these changes to take effect.
 

azure-sql/managed-instance/managed-instance-link-use-scripts-to-replicate-database.md

@@ -61,11 +61,11 @@ As you run scripts from this user guide, it's important not to mistake SQL Serve
 
 ## Set up database recovery and backup
 
-All databases that will be replicated via the link must be in full recovery mode and have at least one backup. Run the following code on SQL Server for all databases you wish to replicate. Replace `<DatabaseName>` with your actual database name.
+All databases that will be replicated via the link must be in the full recovery model and have at least one backup. Run the following code on SQL Server for all databases you wish to replicate. Replace `<DatabaseName>` with your actual database name.
 
 ```sql
 -- Run on SQL Server
--- Set full recovery mode for all databases you want to replicate.
+-- Set full recovery model for all databases you want to replicate.
 ALTER DATABASE [<DatabaseName>] SET RECOVERY FULL
 GO
 

azure-sql/managed-instance/managed-instance-link-use-ssms-to-replicate-database.md

@@ -32,7 +32,7 @@ To replicate your databases to SQL Managed Instance through the link, you need t
 
 ### Set up database recovery and backup
 
-All databases that will be replicated via the link must be in full recovery mode and have at least one full backup. Use SSMS to back up your database. Follow these steps:
+All databases that will be replicated via the link must be in the full recovery model and have at least one full backup. Use SSMS to back up your database. Follow these steps:
 
 1. In SSMS, right-click on a database name on SQL Server
 1. Select Tasks, and then click on Backup Up.

azure-sql/managed-instance/transact-sql-tsql-differences-sql-server.md

@@ -436,7 +436,7 @@ The following database options are set or overridden and can't be changed later:
 - `NEW_BROKER` if the broker isn't enabled in the .bak file. 
 - `ENABLE_BROKER` if the broker isn't enabled in the .bak file. 
 - `AUTO_CLOSE=OFF` if a database in the .bak file has `AUTO_CLOSE=ON`. 
-- `RECOVERY FULL` if a database in the .bak file has `SIMPLE` or `BULK_LOGGED` recovery mode.
+- `RECOVERY FULL` if a database in the .bak file has `SIMPLE` or `BULK_LOGGED` recovery model.
 - A memory-optimized filegroup is added and called XTP if it wasn't in the source .bak file. 
 - Any existing memory-optimized filegroup is renamed to XTP. 
 - `SINGLE_USER` and `RESTRICTED_USER` options are converted to `MULTI_USER`.

azure-sql/virtual-machines/linux/rhel-high-availability-stonith-tutorial.md

@@ -914,7 +914,7 @@ The following Transact-SQL commands are used in this step. Run these commands on
 CREATE DATABASE [db1]; -- creates a database named db1
 GO
 
-ALTER DATABASE [db1] SET RECOVERY FULL; -- set the database in full recovery mode
+ALTER DATABASE [db1] SET RECOVERY FULL; -- set the database in full recovery model
 GO
 
 BACKUP DATABASE [db1] -- backs up the database to disk

azure-sql/virtual-machines/linux/sles-high-availability-stonith-tutorial.md

@@ -1078,7 +1078,7 @@ The following Transact-SQL commands are used in this step. Run these commands on
 CREATE DATABASE [db1]; -- creates a database named db1
 GO
 
-ALTER DATABASE [db1] SET RECOVERY FULL; -- set the database in full recovery mode
+ALTER DATABASE [db1] SET RECOVERY FULL; -- set the database in full recovery model
 GO
 
 BACKUP DATABASE [db1] -- backs up the database to disk

azure-sql/virtual-machines/windows/automated-backup.md

@@ -58,7 +58,7 @@ The following table describes the options that can be configured for Automated B
 
 | Setting | Range (Default) | Description |
 | --- | --- | --- |
-| **System Database Backups** | Enable/Disable (Disabled) | When enabled, this feature also backs up the system databases: `master`, `msdb`, and `model`. For the `msdb` and `model` databases, verify that they are in full recovery mode if you want log backups to be taken. Log backups are never taken for `master`, and no backups are taken for `tempdb`. |
+| **System Database Backups** | Enable/Disable (Disabled) | When enabled, this feature also backs up the system databases: `master`, `msdb`, and `model`. For the `msdb` and `model` databases, verify that they are in the full recovery model if you want log backups to be taken. Log backups are never taken for `master`, and no backups are taken for `tempdb`. |
 | **Backup Schedule** | Manual/Automated (Automated) | By default, the backup schedule is automatically determined based on the log growth. Manual backup schedule allows the user to specify the time window for backups. In this case, backups only take place at the specified frequency and during the specified time window of a given day. |
 | **Full backup frequency** | Daily/Weekly | Frequency of full backups. In both cases, full backups begin during the next scheduled time window. When weekly is selected, backups could span multiple days until all databases have successfully backed up. |
 | **Full backup start time** | 00:00 – 23:00 (01:00) | Start time of a given day during which full backups can take place. |

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

@@ -221,7 +221,7 @@ To create a database, follow these steps:
 1. Open **SQL Server Management Studio** and connect to the SQL Server instance.
 1. In **Object Explorer**, right-click **Databases** and select **New Database**.
 1. In **Database name**, type **MyDB1**.
-1. Select the **Options** page, and choose **Full** from the **Recovery model** drop-down, if it's not full by default. The database must be in full recovery mode to meet the prerequisites of participating in an availability group.
+1. Select the **Options** page, and choose **Full** from the **Recovery model** drop-down, if it's not full by default. The database must be in the full recovery model to meet the prerequisites of participating in an availability group.
 1. Select **OK** to close the **New Database** page and create your new database.
 
 To back up the database, follow these steps:
@@ -274,7 +274,7 @@ To create your availability group, follow these steps.
 
     :::image type="content" source="./media/availability-group-manually-configure-tutorial-multi-subnet/12-new-ag-name.png" alt-text="New availability group Wizard, Specify availability group Name":::
 
-1. On the **Select Databases** page, select your database, and then select **Next**. If your database does not meet the prerequisites, make sure it's in full recovery mode, and [take a backup](#create-database):
+1. On the **Select Databases** page, select your database, and then select **Next**. If your database does not meet the prerequisites, make sure it's in the full recovery model, and [take a backup](#create-database):
 
    :::image type="content" source="./media/availability-group-manually-configure-tutorial-multi-subnet/13-new-ag-select-database.png" alt-text="New availability group Wizard, Select Databases":::
 

docs/big-data-cluster/deployment-high-availability.md

@@ -182,7 +182,7 @@ Here is an example that shows how to expose this endpoint and then add the datab
 
 - Add the database to the availability group.
 
-    For the database to be added to the AG, it has to run in full recovery mode and a log backup has to be taken. Use the IP from the Kubernetes service created above and connect to the SQL Server instance then run the TSQL statements as shown below.
+    For the database to be added to the AG, it has to run in the full recovery model and a log backup has to be taken. Use the IP from the Kubernetes service created above and connect to the SQL Server instance then run the T-SQL statements as shown below.
 
     ```sql
     ALTER DATABASE <databaseName> SET RECOVERY FULL;

docs/database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability.md

@@ -333,8 +333,8 @@ helpviewer_keywords:
 |Be a read-write database. Read-only databases cannot be added to an availability group.|[sys.databases](../../../relational-databases/system-catalog-views/sys-databases-transact-sql.md) (**is_read_only** = 0)|  
 |Be a multi-user database.|[sys.databases](../../../relational-databases/system-catalog-views/sys-databases-transact-sql.md) (**user_access** = 0)|  
 |Not use AUTO_CLOSE.|[sys.databases](../../../relational-databases/system-catalog-views/sys-databases-transact-sql.md) (**is_auto_close_on** = 0)|  
-|Use the full recovery model (also known as, full recovery mode).|[sys.databases](../../../relational-databases/system-catalog-views/sys-databases-transact-sql.md) (**recovery_model** = 1)|  
-|Possess at least one full database backup.<br /><br /> Note: After setting a database to full recovery mode, a full backup is required to initiate the full-recovery log chain.|[Create a Full Database Backup &#40;SQL Server&#41;](../../../relational-databases/backup-restore/create-a-full-database-backup-sql-server.md)|  
+|Use the full recovery model.|[sys.databases](../../../relational-databases/system-catalog-views/sys-databases-transact-sql.md) (**recovery_model** = 1)|  
+|Possess at least one full database backup.<br /><br /> Note: After setting a database to full recovery model, a full backup is required to initiate the full-recovery log chain.|[Create a Full Database Backup &#40;SQL Server&#41;](../../../relational-databases/backup-restore/create-a-full-database-backup-sql-server.md)|  
 |Not belong to any existing availability group.|[sys.databases](../../../relational-databases/system-catalog-views/sys-databases-transact-sql.md) (**group_database_id** = NULL)|  
 |Not be configured for database mirroring.|[sys.database_mirroring](../../../relational-databases/system-catalog-views/sys-database-mirroring-transact-sql.md) (If the database does not participate in mirroring, all columns prefixed with "mirroring_" are NULL.)|  
 |Before adding a database that uses FILESTREAM to an availability group, ensure that FILESTREAM is enabled on every server instance that hosts or will host an availability replica for the availability group.|[Enable and Configure FILESTREAM](../../../relational-databases/blob/enable-and-configure-filestream.md)|