4/17/2025 PM Publish (#33843)

* SUBSTRING enhancements for Azure SQL

* [Azure SQL Database] Copilot GA release

* Fabric changes for sp-rename and ALTER TABLE articles

* [Azure SQL Database]  Copilot GA release

* made edits to the FAQ and removed some sample prompts

* remove erroneous file

* Moved the table of copilot prompts to a separate file and linked to it from the over view file

* move the note

* edit table file

* acrolinx improvement

* add description to prompt file

* Removed all references to preview

* edit best practices section

* fix broken link

* remove line 78

* add to tOC

* Update docs/t-sql/statements/alter-table-transact-sql.md

* update metadata

* edit intro paragraph and H1 title

* minor edits

* add migration tags

* minor edits

* add an additional link to related content area

* Update create-user-transact-sql.md

Sid + type is also on Azure SQL Database

* Update authentication-azure-ad-user-assigned-managed-identity.md

Update the SMI portion of the Azure SQL DB to make use of the sid+type syntax.

* Learn Editor: Update create-view-transact-sql.md

* update Metadata

* Learn Editor: Update create-view-transact-sql.md

* Learn Editor: Update grant-object-permissions-transact-sql.md

* update Metadata

* Learn Editor: Update grant-object-permissions-transact-sql.md

* correct typos and add question back to FAQ

* [Azure SQL Database] more copilot edits

* acrolinx improvement

* acrolinx improvements

* some more branding changes and minor edits

* remove additional include file

* pulling PRs to private

* edit

* [Azure SQL Database] minor edits and updates

* Added missing column in output table

Added the missing 'job_name' column in the output table.

* Minor improvements

* Apply suggestions from code review

Co-authored-by: Chad Kittel <[email protected]>

* At-scale migration assessment for SQL Server enabled by Azure Arc

* Staging IO Analysis GA

* Update docs/t-sql/statements/grant-object-permissions-transact-sql.md

Co-authored-by: Van To <[email protected]>

* 20250409 schemabinding

* Confirm merge from FromPublicRepo to main to sync with https://github.com/MicrosoftDocs/sql-docs (branch live) (#33773)

* 4/8/2025 AM Publish (#33752)

* Fix include file and refresh associated articles

* [SCOPED] SQL Tools content: Update author, add ms.collection, fix metadata

* added edge case when the parameter is 0

* Edit pass

* Update sys-databases-transact-sql.md

* Merge pull request #33738 from MicrosoftDocs/release-azure-sql-copilot-ga

[Azure SQL Database] Azure SQL Database Copilot - Release branch to main 04/08/2025 @ 1030am PST

---------

Co-authored-by: Randolph West MSFT <[email protected]>
Co-authored-by: James Barnett <[email protected]>
Co-authored-by: YanoOfQueenscastle <[email protected]>
Co-authored-by: TWINKLE CYRIL <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Mark Ghanayem <[email protected]>

* Added missing column in output table

Added the missing 'job_name' column in the output table.

---------

Co-authored-by: Bo wen Yang <[email protected]>
Co-authored-by: Randolph West MSFT <[email protected]>
Co-authored-by: James Barnett <[email protected]>
Co-authored-by: YanoOfQueenscastle <[email protected]>
Co-authored-by: TWINKLE CYRIL <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Mark Ghanayem <[email protected]>
Co-authored-by: finnigd <[email protected]>

* correct conflict

* reworked the order

* Update docs/t-sql/statements/create-view-transact-sql.md

Co-authored-by: Mark Ghanayem <[email protected]>

* 20250409 1059 edit pass

* 20250409 edit pass acrolinx

* Updated steps for NSP (#33759)

* Updated steps for NSP

* Fixed image path

* review and remove sensitive info

* edit

* rename image resources

---------

Co-authored-by: VanMSFT <[email protected]>

* Remove a fixed known issue

* Correct extra script contents info (#33787)

* SQL tools content freshness pass (#33754)

Co-authored-by: Erin Stellato <[email protected]>

* Update import-flat-file-wizard.md (#10062)

* Update .NET passwordless flow

update tabs

simplify code

* Edit pass

* Update azure-sql/virtual-machines/windows/storage-performance-analysis.md

* Add a best practice for dropping resource pools (#33783)

* Update sql-server-linux-configure-mssql-conf.md (#33728)

* Update create-function-transact-sql.md

Immaterial Revision

Schema Binding Section

The binding of the function to the objects it references is removed only when one of the following actions occurs:


The binding of the function to the objects it references is removed only when ne of the following actions occurs:

* Update create-columnstore-index-transact-sql.md (#33798)

* Updated for serverless (#33794)

* Update sys-dm-db-missing-index-group-stats-query-transact-sql.md

Removing the note from the remarks section.

* Learn Editor: Update authentication-azure-ad-user-assigned-managed-identity.md

* Learn Editor: Update authentication-azure-ad-user-assigned-managed-identity.md

* Edit pass

* Applying changes from review

* 170 release notes

* Update parameter-sensitive-plan-optimization.md

Update query hint

* Remove duplicate use hint documentation (#33815)

* Update substring syntax.

* [PLEASE SQUASH] Staging lrs & mi link comparison (#33747)

* Staging lrs & mi link comparison

* fixing link

* Update sys-fulltext-catalogs-transact-sql.md

* SqlPackage with Parquet files (#33819)

Co-authored-by: Randolph West MSFT <[email protected]>

* Update replication-security-best-practices.md

Based on chat with Sasa Popovic

* Light upgrade refresh (UUF 419735)

* Refresh master database restore article (UUF 420834) (#33842)

---------

Co-authored-by: Randolph West MSFT <[email protected]>
Co-authored-by: Mark Ghanayem <[email protected]>
Co-authored-by: Alma Jenks <[email protected]>
Co-authored-by: TWINKLE CYRIL <[email protected]>
Co-authored-by: Jodi Martis <[email protected]>
Co-authored-by: James Barnett <[email protected]>
Co-authored-by: Pratim Dasgupta <[email protected]>
Co-authored-by: chroux <[email protected]>
Co-authored-by: VanMSFT <[email protected]>
Co-authored-by: finnigd <[email protected]>
Co-authored-by: Jovan Popovic (MSFT) <[email protected]>
Co-authored-by: Chad Kittel <[email protected]>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Ajith Krishnan <[email protected]>
Co-authored-by: Masha MSFT <[email protected]>
Co-authored-by: Regan Downer <[email protected]>
Co-authored-by: William Assaf MSFT <[email protected]>
Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>
Co-authored-by: YanoOfQueenscastle <[email protected]>
Co-authored-by: Learn Build Service GitHub App <Learn Build Service [email protected]>
Co-authored-by: Jill Grant <[email protected]>
Co-authored-by: sudhanshukhera <[email protected]>
Co-authored-by: Dimitri Furman <[email protected]>
Co-authored-by: Drew Skwiers-Koballa <[email protected]>
Co-authored-by: Erin Stellato <[email protected]>
Co-authored-by: Steve Jones <[email protected]>
Co-authored-by: Alex Wolf <[email protected]>
Co-authored-by: Nicolas Blais Miko <[email protected]>
Co-authored-by: Daniel Adeniji <[email protected]>
Co-authored-by: David Levy <[email protected]>
Co-authored-by: mhyon <[email protected]>
Co-authored-by: Derek Wilson <[email protected]>
Co-authored-by: Drew Skwiers-Koballa <[email protected]>
Co-authored-by: Mike Ray <[email protected]>

Author: 34 people

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)