Merging changes synced from https://github.com/MicrosoftDocs/sql-docs-pr (branch live)

Author: Learn Build Service GitHub App

docs/database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup.md

@@ -3,7 +3,7 @@ title: "Upgrade: Installation Wizard (Setup)"
 description: The SQL Server Installation Wizard provides a single feature tree for an in-place upgrade of SQL Server components to the latest version of SQL Server.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 10/31/2024
+ms.date: 04/17/2025
 ms.service: sql
 ms.subservice: install
 ms.topic: install-set-up-deploy
@@ -21,9 +21,7 @@ monikerRange: ">=sql-server-2016"
 The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation Wizard provides a single feature tree for an in-place upgrade of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] components to the latest version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)].
 
 > [!WARNING]  
-> When you upgrade [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], the previous version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is overwritten, and no longer exists on your computer.
->
-> Before upgrading, back up SQL Server databases and other objects associated with the previous SQL Server instance.
+> When you upgrade [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], the previous version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is overwritten, and no longer exists on your computer. Before upgrading, back up SQL Server databases and other objects associated with the previous SQL Server instance.
 
 For many production and some development environments, a new installation upgrade or a rolling upgrade is more appropriate than an in-place upgrade. For more information regarding upgrade methods, see:
 
@@ -40,7 +38,7 @@ For many production and some development environments, a new installation upgrad
 You must run Setup as an administrator. If you install [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] from a remote share, you must use a domain account that has read and execute permissions on the remote share, and is a local administrator.
 
 > [!WARNING]  
-> Be aware that you can't change the features to be upgraded, and you can't add features during the upgrade operation. For more information about how to add features to an upgraded instance of [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] after the upgrade operation is complete, see [Add Features to an Instance of SQL Server (Setup)](add-features-to-an-instance-of-sql-server-setup.md).
+> You can't change the features to be upgraded, and you can't add features during the upgrade operation. For more information about how to add features to an upgraded instance of [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] after the upgrade operation is complete, see [Add Features to an Instance of SQL Server (Setup)](add-features-to-an-instance-of-sql-server-setup.md).
 
 If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Plan and test the Database Engine upgrade plan](plan-and-test-the-database-engine-upgrade-plan.md) and then perform the following tasks, as appropriate for your environment:
 
@@ -52,7 +50,7 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
 
 - Ensure that existing SQL Server system databases - master, model, `msdb`, and `tempdb` - are configured to autogrow, and ensure that they have sufficient hard disk space.
 
-- Ensure that all database servers have logon information in the `master` database. This is important for restoring a database, as system logon information resides in master.
+- Ensure that all database servers have logon information in the `master` database. This is important for restoring a database, as system logon information resides in `master`.
 
 - Disable all startup stored procedures, as the upgrade process stops and starts services on the SQL Server instance being upgraded. Stored procedures processed at startup time might block the upgrade process.
 
@@ -67,7 +65,7 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
 
 <a id="to-upgrade-include-ssnoversionincludesssnoversion-mdmd"></a>
 
-### Upgrade [!INCLUDE [ssNoversion](../../includes/ssnoversion-md.md)]
+### Upgrade SQL Server
 
 1. Insert the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] installation media, and from the root folder, double-click Setup.exe. To install from a network share, move to the root folder on the share, and then double-click Setup.exe.
 
@@ -94,7 +92,7 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
    The prerequisites for the selected features are displayed on the right-hand pane. [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Setup installs the prerequisites that aren't already installed during the installation step described later in this procedure.
 
    > [!NOTE]  
-   > If you have opted to upgrade the shared features by selecting **\<Upgrade shared features only>** on the **Select Instance** page, all the shared features are preselected on the Feature Selection page. All the shared components are upgraded at the same time.
+   > If you elect to upgrade the shared features by selecting **\<Upgrade shared features only>** on the **Select Instance** page, all the shared features are preselected on the Feature Selection page. All the shared components are upgraded at the same time.
 
 1. On the Instance Configuration page, specify the Instance ID for the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)].
 
@@ -112,7 +110,7 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
 
    To specify the same login account for all service accounts in this instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], provide credentials in the fields at the bottom of the page.
 
-   > [!CAUTION]
+   > [!CAUTION]  
    > [!INCLUDE [ssNoteStrongPass](../../includes/ssnotestrongpass-md.md)]
 
      When you're finished specifying login information for [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] services, select **Next**.
@@ -127,9 +125,10 @@ If you're upgrading the [!INCLUDE [ssDE](../../includes/ssde-md.md)], review [Pl
 
 1. After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] installation process, select **Close**.
 
-1. If you're instructed to restart the computer, do so now. It's important to read the message from the Installation Wizard when you have finished with Setup. For more information about Setup log files, see [View and Read SQL Server Setup Log Files](view-and-read-sql-server-setup-log-files.md).
+1. If you're instructed to restart the computer, do so now. You must read the message from the Installation Wizard when you finish with Setup. For more information about Setup log files, see [View and Read SQL Server Setup Log Files](view-and-read-sql-server-setup-log-files.md).
 
 ## Related content
 
 - [Upgrade SQL Server](upgrade-sql-server.md)
-- [Backward Compatibility_deleted](/previous-versions/sql/sql-server-2016/cc280407(v=sql.130))
+- [Issues when upgrading to SQL Server 2022](/troubleshoot/sql/database-engine/install/windows/issues-upgrading-sql-server-2022)
+- [Backward Compatibility](/previous-versions/sql/sql-server-2016/cc280407(v=sql.130))

docs/relational-databases/backup-restore/restore-the-master-database-transact-sql.md

@@ -1,9 +1,10 @@
 ---
-title: "Restore the master database (Transact-SQL)"
+title: "Restore the master Database (Transact-SQL)"
 description: This article shows you how to restore the master database in SQL Server from a full database backup by using Transact-SQL.
 author: MashaMSFT
 ms.author: mathoma
-ms.date: "12/07/2022"
+ms.reviewer: randolphwest
+ms.date: 04/17/2025
 ms.service: sql
 ms.subservice: backup-restore
 ms.topic: how-to
@@ -12,21 +13,21 @@ helpviewer_keywords:
 ---
 # Restore the master database (Transact-SQL)
 
- [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
+[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-  This article explains how to restore the `master` database from a full database backup.
+This article explains how to restore the `master` database from a full database backup.
+
+> [!WARNING]  
+> In the event of disaster recovery, the instance where the `master` database is being restored to should be as close to an exact match to the original as possible. At a minimum, this recovery instance should be the same version, edition, and patch level, and it should have the same selection of features and the same external configuration (hostname, cluster membership, and so on) as the original instance. Doing otherwise can result in undefined SQL Server instance behavior, with inconsistent feature support, and isn't guaranteed to be viable.
+
+## Restore the `master` database
+
+1. Start the server instance in single-user mode.
+
+   You can start SQL Server by either using the `-m` or `-f` startup parameters. For more information about startup parameters, see [Database Engine Service startup options](../../database-engine/configure-windows/database-engine-service-startup-options.md).
 
-> [!WARNING]
-> In the event of disaster recovery, the instance where the `master` database is being restored to should be as close to an exact match to the original as possible. At a minimum, this recovery instance should be the same version, edition, and patch level, and it should have the same selection of features and the same external configuration (hostname, cluster membership, and so on) as the original instance. Doing otherwise might result in undefined SQL Server instance behavior, with inconsistent feature support, and is not guaranteed to be viable.
-  
-### To restore the `master` database
-  
-1. Start the server instance in single-user mode.  
-  
-   You can start SQL Server by either using the `-m` or `-f` startup parameters. For more information about startup parameters, see [Database Engine Service Startup Options](../../database-engine/configure-windows/database-engine-service-startup-options.md).
-   
    From a command prompt, run the following commands, and make sure you replace `MSSQLXX.instance` with the appropriate folder name:
-  
+
    ```console
    cd C:\Program Files\Microsoft SQL Server\MSSQLXX.instance\MSSQL\Binn
    sqlservr -c -f -s <instance> -mSQLCMD
@@ -35,52 +36,51 @@ helpviewer_keywords:
    - The `-mSQLCMD` parameter ensures that only **sqlcmd** can connect to SQL Server.
    - For a default instance name, use `-s MSSQLSERVER`
    - `-c` starts SQL Server as an application to bypass Service Control Manager to shorten startup time
-  
+
    If the SQL Server instance can't start due to a damaged `master` database, you must rebuild the system databases first. For more information, see [Rebuild system databases](../databases/rebuild-system-databases.md).
 
-1. Connect to SQL Server using SQLCMD from another Command Prompt window
+1. Connect to SQL Server using **sqlcmd** from another command prompt window:
 
    ```console
-   SQLCMD -S <instance> -E -d master
+   sqlcmd -S <instance> -E -d master
+   ```
+
+1. To restore a full database backup of `master`, use the following [RESTORE Statements](../../t-sql/statements/restore-statements-transact-sql.md)[!INCLUDE [tsql](../../includes/tsql-md.md)] statement:
+
+   ```sql
+   RESTORE DATABASE master FROM <backup_device> WITH REPLACE;
    ```
 
-1. To restore a full database backup of **master**, use the following [RESTORE DATABASE](../../t-sql/statements/restore-statements-transact-sql.md)[!INCLUDE[tsql](../../includes/tsql-md.md)] statement:  
-  
-    ```sql
-    RESTORE DATABASE master FROM  <backup_device>  WITH REPLACE
-    ```
-  
-     The REPLACE option instructs [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to restore the specified database even when a database of the same name already exists. The existing database, if any, is deleted. In single-user mode, we recommend that you enter the RESTORE DATABASE statement in the [sqlcmd utility](../../tools/sqlcmd/sqlcmd-utility.md). For more information, see [Use the sqlcmd Utility](../../tools/sqlcmd/sqlcmd-use-utility.md).  
-  
-    > [!IMPORTANT]  
-    >  After **master** is restored, the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] shuts down and terminates the **sqlcmd** process. Before you restart the server instance, remove the single-user startup parameter. For more information, see [Configure Server Startup Options &#40;SQL Server Configuration Manager&#41;](../../database-engine/configure-windows/scm-services-configure-server-startup-options.md).  
+   The `REPLACE` option instructs [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] to restore the specified database even when a database of the same name already exists. The existing database, if any, is deleted. In single-user mode, we recommend that you enter the `RESTORE DATABASE` statement in the [sqlcmd utility](../../tools/sqlcmd/sqlcmd-utility.md). For more information, see [Use sqlcmd](../../tools/sqlcmd/sqlcmd-use-utility.md).
+
+   > [!IMPORTANT]  
+   > After `master` is restored, the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] shuts down and terminates the `sqlcmd` process. Before you restart the server instance, remove the single-user startup parameter. For more information, see [SQL Server Configuration Manager: Configure server startup options](../../database-engine/configure-windows/scm-services-configure-server-startup-options.md).
+
+1. Restart the server instance normally as a service, without using any startup parameters.
 
+1. Continue other recovery steps such as restoring other databases, attaching databases, and correcting user mismatches.
 
-1. Restart the server instance normally as a service, without using any startup parameters. 
-1. Continue other recovery steps such as restoring other databases, attaching databases, and correcting user mismatches.  
-  
-## Example
+## Examples
 
-The following example restores the `master` database on the default server instance. The example assumes that the server instance is already running in single-user mode. The example starts `sqlcmd` and executes a `RESTORE DATABASE` statement that restores a full database backup of `master` from a disk device: `Z:\SQLServerBackups\master.bak`.  
-  
- > [!NOTE]  
- > For a named instance, the **sqlcmd** command must specify the **-S**_\<ComputerName>_\\*\<InstanceName>* option.
+The following example restores the `master` database on the default server instance. The example assumes that the server instance is already running in single-user mode. The example starts **sqlcmd** and executes a `RESTORE DATABASE` statement that restores a full database backup of `master` from a disk device: `Z:\SQLServerBackups\master.bak`.
+
+For a named instance, the **sqlcmd** command must specify the `-S<computer-name>\<instance-name>` option.
 
 ```console
-C:\> sqlcmd  
-1> RESTORE DATABASE master FROM DISK = 'Z:\SQLServerBackups\master.bak' WITH REPLACE;  
-2> GO  
-```  
-  
-## See Also
-
- [Complete Database Restores &#40;Simple Recovery Model&#41;](../../relational-databases/backup-restore/complete-database-restores-simple-recovery-model.md)   
- [Complete Database Restores &#40;Full Recovery Model&#41;](../../relational-databases/backup-restore/complete-database-restores-full-recovery-model.md)   
- [Troubleshoot Orphaned Users &#40;SQL Server&#41;](../../sql-server/failover-clusters/troubleshoot-orphaned-users-sql-server.md)   
- [Database Detach and Attach &#40;SQL Server&#41;](../../relational-databases/databases/database-detach-and-attach-sql-server.md)   
- [Rebuild System Databases](../../relational-databases/databases/rebuild-system-databases.md)   
- [Database Engine Service Startup Options](../../database-engine/configure-windows/database-engine-service-startup-options.md)   
- [SQL Server Configuration Manager](../../relational-databases/sql-server-configuration-manager.md)   
- [Back Up and Restore of System Databases &#40;SQL Server&#41;](../../relational-databases/backup-restore/back-up-and-restore-of-system-databases-sql-server.md)   
- [RESTORE &#40;Transact-SQL&#41;](../../t-sql/statements/restore-statements-transact-sql.md)   
-- [Start SQL Server in Single-User Mode](../../database-engine/configure-windows/start-sql-server-in-single-user-mode.md)
+C:\> sqlcmd
+1> RESTORE DATABASE master FROM DISK = 'Z:\SQLServerBackups\master.bak' WITH REPLACE;
+2> GO
+```
+
+## Related content
+
+- [Complete Database Restores (Simple Recovery Model)](complete-database-restores-simple-recovery-model.md)
+- [Complete Database Restores (Full Recovery Model)](complete-database-restores-full-recovery-model.md)
+- [Troubleshoot orphaned users (SQL Server)](../../sql-server/failover-clusters/troubleshoot-orphaned-users-sql-server.md)
+- [Database detach and attach (SQL Server)](../databases/database-detach-and-attach-sql-server.md)
+- [Rebuild system databases](../databases/rebuild-system-databases.md)
+- [Database Engine Service startup options](../../database-engine/configure-windows/database-engine-service-startup-options.md)
+- [SQL Server Configuration Manager](../../relational-databases/sql-server-configuration-manager.md)
+- [Back up and restore: System databases (SQL Server)](back-up-and-restore-of-system-databases-sql-server.md)
+- [RESTORE Statements (Transact-SQL)](../../t-sql/statements/restore-statements-transact-sql.md)
+- [Single-user mode for SQL Server](../../database-engine/configure-windows/start-sql-server-in-single-user-mode.md)