4/11/2025 AM Publish (#33795)

* [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

* 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

* [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 <chad.kittel@gmail.com>

* 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 <40007119+VanMSFT@users.noreply.github.com>

* 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 <97149825+rwestMSFT@users.noreply.github.com>
Co-authored-by: James Barnett <v-jabarnett@microsoft.com>
Co-authored-by: YanoOfQueenscastle <151081922+YanoOfQueenscastle@users.noreply.github.com>
Co-authored-by: TWINKLE CYRIL <53920725+twinklecyril@users.noreply.github.com>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Mark Ghanayem <22989000+markingmyname@users.noreply.github.com>

* Added missing column in output table

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

---------

Co-authored-by: Bo wen Yang <160521015+Albertyang0@users.noreply.github.com>
Co-authored-by: Randolph West MSFT <97149825+rwestMSFT@users.noreply.github.com>
Co-authored-by: James Barnett <v-jabarnett@microsoft.com>
Co-authored-by: YanoOfQueenscastle <151081922+YanoOfQueenscastle@users.noreply.github.com>
Co-authored-by: TWINKLE CYRIL <53920725+twinklecyril@users.noreply.github.com>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Mark Ghanayem <22989000+markingmyname@users.noreply.github.com>
Co-authored-by: finnigd <138986077+finnigd@users.noreply.github.com>

* correct conflict

* reworked the order

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

Co-authored-by: Mark Ghanayem <22989000+markingmyname@users.noreply.github.com>

* 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 <40007119+VanMSFT@users.noreply.github.com>

* Remove a fixed known issue

* Correct extra script contents info (#33787)

* SQL tools content freshness pass (#33754)

Co-authored-by: Erin Stellato <98599126+erinstellato-ms@users.noreply.github.com>

* 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)

---------

Co-authored-by: Mark Ghanayem <22989000+markingmyname@users.noreply.github.com>
Co-authored-by: Alma Jenks <v-alje@microsoft.com>
Co-authored-by: TWINKLE CYRIL <53920725+twinklecyril@users.noreply.github.com>
Co-authored-by: Randolph West MSFT <97149825+rwestMSFT@users.noreply.github.com>
Co-authored-by: Jodi Martis <v-jodimartis@microsoft.com>
Co-authored-by: James Barnett <v-jabarnett@microsoft.com>
Co-authored-by: chroux <116909371+chopsakie@users.noreply.github.com>
Co-authored-by: finnigd <138986077+finnigd@users.noreply.github.com>
Co-authored-by: Jovan Popovic (MSFT) <jovanpop@microsoft.com>
Co-authored-by: Chad Kittel <chad.kittel@gmail.com>
Co-authored-by: prmerger-automator[bot] <40007230+prmerger-automator[bot]@users.noreply.github.com>
Co-authored-by: Ajith Krishnan <61177957+ajithkr-ms@users.noreply.github.com>
Co-authored-by: Masha MSFT <32783170+MashaMSFT@users.noreply.github.com>
Co-authored-by: Regan Downer <v-rdowner@microsoft.com>
Co-authored-by: William Assaf MSFT <74387232+WilliamDAssafMSFT@users.noreply.github.com>
Co-authored-by: Van To <40007119+VanMSFT@users.noreply.github.com>
Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com>
Co-authored-by: YanoOfQueenscastle <151081922+YanoOfQueenscastle@users.noreply.github.com>
Co-authored-by: Learn Build Service GitHub App <Learn Build Service LearnBuild@microsoft.com>
Co-authored-by: Jill Grant <72043882+JillGrant615@users.noreply.github.com>
Co-authored-by: sudhanshukhera <skhera@microsoft.com>
Co-authored-by: Dimitri Furman <dfurman@microsoft.com>
Co-authored-by: Drew Skwiers-Koballa <dzsquared@users.noreply.github.com>
Co-authored-by: Erin Stellato <98599126+erinstellato-ms@users.noreply.github.com>
Co-authored-by: Steve Jones <steve.jones@red-gate.com>
Co-authored-by: Alex Wolf <alexwolf@microsoft.com>
Co-authored-by: Nicolas Blais Miko <nicolas.blais-miko@polymtl.ca>

Author: 28 people

azure-sql/database/azure-sql-dotnet-entity-framework-core-quickstart.md

@@ -160,7 +160,7 @@ The following lists potential causes for latency without throttling:
 - **Background processes**: Other processes on the VM - such as antivirus software, backups, or maintenance tasks (like Windows Update) - can consume CPU, memory, or disk I/O resources, which delay SQL Server operations. Inefficient filter drivers can worsen this effect. These processes compete with SQL Server for system resources, causing I/O delays that appear as storage latency. For instance, an antivirus scan that reads numerous files simultaneously can reduce disk bandwidth available to SQL Server, which increase latency for database transactions. Additionally, not having the right antivirus exclusions can introduce latency issues without throttling in SQL Server on Azure VMs, primarily through increased disk I/O, filter driver interference, and resource competition.
 - **Lower tiered storage usage**: Opting for lower-tier storage options, such as Standard HDDs, instead of Premium SSDs or Ultra Disks, introduces higher baseline latency due to the inherent design of these disks, even without hitting IOPS limits. While cost-effective, lower-tier storage is not optimized for performance-sensitive SQL Server workloads, which leads to slower data access. For example, a customer using Standard HDDs to save costs might experience slower query performance due to the disks' naturally higher latency.
 - **Inadequate storage configuration**: Failing to configure your storage to optimize for SQL Server workloads can lead to latency without throttling. For example, incorrect disk caching settings can degrade performance. Microsoft recommends enabling read-only caching for data disks and disabling caching for log disks when using Premium SSD v1 with SQL Server on Azure VMs. Misconfigured caching can slow down read or write operations. For example, disabling read caching on a data disk that hosts SQL Server data files reduces the efficiency of read-heavy workloads, increasing latency.
-- **SQL Server database contention**: Inefficient queries (for example, a full table scan instead of an indexed lookups) or lock contention within SQL Server can increase I/O demand or delay data access, which manifests as storage latency. Application-level issues can strain the storage subsystem without exceeding its limits, particularly with small, random I/O patterns common in transactional workloads. For example, a poorly optimized query that performs a full table scan on a large dataset will read excessive data from disk, boosting I/O load and latency compared to an indexed query.
+- **SQL Server database contention**: Inefficient queries (for example, a full table scan instead of an indexed lookup) or lock contention within SQL Server can increase I/O demand or delay data access, which manifests as storage latency. Application-level issues can strain the storage subsystem without exceeding its limits, particularly with small, random I/O patterns common in transactional workloads. For example, a poorly optimized query that performs a full table scan on a large dataset will read excessive data from disk, boosting I/O load and latency compared to an indexed query.
 
 If you're experiencing latency without throttling, consider the following steps to address the latency: 
 

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

@@ -3,7 +3,7 @@ title: Configure SQL Server Settings on Linux
 description: This article describes how to use the mssql-conf tool to configure SQL Server settings on Linux.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 11/18/2024
+ms.date: 04/09/2025
 ms.service: sql
 ms.subservice: linux
 ms.topic: install-set-up-deploy
@@ -233,6 +233,13 @@ The following options are used by Microsoft Entra authentication for an instance
 > [!WARNING]  
 > Microsoft Entra ID parameters are configured by the Azure extension for [!INCLUDE [ssnoversion-md](../includes/ssnoversion-md.md)], and shouldn't be reconfigured manually. They are listed here for informational purposes.
 
+[!INCLUDE [sssql22-md](../includes/sssql22-md.md)] CU 19 introduces an option to set the IPv6 records limit for Microsoft Entra authentication endpoints. If IPv6 is enabled on Linux, and the IPv6 addresses of the Microsoft Entra authentication endpoints aren't reachable, you can set the [network.ipv6dnsrecordslimit](#ipv6dnsrecordslimit) option for Microsoft Entra authentication to work. Setting this option to any value between `0` and `5` guarantees that at least one IPv4 address is tried to reach the Microsoft Entra endpoints.
+
+A value of `0` means that no IPv6 endpoint addresses are tried. A value of `5` means that five AAAA addresses are tried.
+
+> [!NOTE]  
+> This `network.ipv6dnsrecordslimit` setting is configured at the server level, and can affect other services that use IPv6.
+
 | Option | Description |
 | --- | --- |
 | `network.aadauthenticationendpoint` | Endpoint for Microsoft Entra authentication |
@@ -870,6 +877,7 @@ The following options are additional network settings configurable using **mssql
 | `network.ipaddress` | IP address for incoming connections. |
 | `network.kerberoscredupdatefrequency` | Time in seconds between checks for kerberos credentials that need to be updated. Value is an integer. |
 | `network.privilegedadaccount` | Privileged Active Directory user to use for Active Directory authentication. Value is `<username>`. For more information, see [Tutorial: Use Active Directory authentication with SQL Server on Linux](sql-server-linux-active-directory-authentication.md#spn) |
+| <a id="ipv6dnsrecordslimit"></a>`network.ipv6dnsrecordslimit` | Set a configurable limit to the number of AAAA records returned by DNS requests. Value is a positive integer between `0` and `5`. This option is guarantees that WinHTTP requests with the default number of retries (6) attempt at least one IPv4 address. |
 | `uncmapping` | Maps UNC path to a local path. For example, `sudo /opt/mssql/bin/mssql-conf set uncmapping //servername/sharename /tmp/folder`. |
 | `ldaphostcanon` | Set whether OpenLDAP should canonicalize hostnames during the bind step. Values can be `true` or `false`. |
 

docs/linux/sql-server-linux-configure-mssql-conf.md

@@ -18,7 +18,7 @@ monikerRange: "=azuresqldb-current || >=sql-server-2016 || >=sql-server-linux-20
 
 > For content related to the Import and Export Wizard, see [Import and Export Data with the SQL Server Import and Export Wizard](../../integration-services/import-export-data/import-and-export-data-with-the-sql-server-import-and-export-wizard.md).
 
-Import Flat File Wizard is a simple way to copy data from a flat file (.csv, .txt) to a new table in your database. The Import Flat File Wizard supports both comma-separated and fixed width format files. This overview describes the reasons for using this wizard, how to find this wizard, and a simple example to follow.
+Import Flat File Wizard is a simple way to copy data from a flat file (for example, .csv or .txt) to a new table in your database. The Import Flat File Wizard supports multiple delimiters, including commas, tabs, semicolons, and pipes, and also supports fixed width data. This overview describes the reasons for using this wizard, how to find this wizard, and a simple example to follow.
 
 ## Why would I use this wizard?
 

docs/relational-databases/import-export/import-flat-file-wizard.md

@@ -4,7 +4,7 @@ description: Learn how to enable resource governor using either SQL Server Manag
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: dfurman
-ms.date: 01/02/2025
+ms.date: 04/09/2025
 ms.service: sql
 ms.subservice: performance
 ms.topic: how-to
@@ -19,6 +19,8 @@ monikerRange: ">= sql-server-2016 || >= sql-server-linux-2017 || = azuresqldb-mi
 
 Resource governor is turned off by default. You can enable resource governor using either [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] or [!INCLUDE[tsql](../../includes/tsql-md.md)].
 
+For configuration and monitoring examples and to learn resource governor best practices, see [Tutorial: Resource governor configuration examples and best practices](resource-governor-walkthrough.md).
+
 Enabling resource governor has the following results:
 
 - The classifier function is executed for new connections so that workloads can be assigned to workload groups.

docs/relational-databases/resource-governor/enable-resource-governor.md

@@ -4,7 +4,7 @@ description: Use examples to learn how to create and validate resource governor
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: dfurman
-ms.date: 03/12/2025
+ms.date: 04/09/2025
 ms.service: sql
 ms.subservice: performance
 ms.topic: tutorial
@@ -506,6 +506,9 @@ GROUP BY wg.name,
 - Avoid using a frequently modified table in the classifier. That increases the risk of blocking that can delay logins and cause connection timeouts. The following workarounds can mitigate the risk, however they have downsides, including the risk of incorrect classification:
     - Consider using the `NOLOCK` table hint, or the equivalent `READUNCOMMITTED` hint. For more information, see [READUNCOMMITTED](../../t-sql/queries/hints-transact-sql-table.md#readuncommitted).
     - Consider using the `LOCK_TIMEOUT` setting at the start of the classifier function, setting it to a low value such as 1,000 milliseconds. For more information, see [SET LOCK_TIMEOUT](../../t-sql/statements/set-lock-timeout-transact-sql.md).
+- If you execute `ALTER RESOURCE GOVERNOR RECONFIGURE` after deleting an unused resource pool on a machine with a large amount of memory, the command might take a long time. If a classifier function is in effect before reconfiguration starts, new connection attempts made during that time might time out.
+
+    If you delete an unused resource pool, we recommend that you reconfigure resource governor during a maintenance window or a period of low activity.
 - You can't modify a classifier function while it is referenced in the resource governor configuration. However, you can modify the configuration to use a different classifier function. If you want to make changes to the classifier, consider creating a pair of classifier functions. For example, you might create `dbo.rg_classifier_A()` and `dbo.rg_classifier_B()`. When a change to the classifier logic is needed, follow these steps:
     1. Use the [ALTER FUNCTION](../../t-sql/statements/alter-function-transact-sql.md) statement to make the changes in the function *not* currently used in the resource governor configuration.
     1. Use the [ALTER RESOURCE GOVERNOR](../../t-sql/statements/alter-resource-governor-transact-sql.md) statement to make the modified classifier active, and then reconfigure resource governor. For example: