4/17/2025 AM Publish (#33833)

* 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

---------

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/relational-databases/replication/security/replication-security-best-practices.md

@@ -63,12 +63,15 @@ helpviewer_keywords:
 
 ## Improve security posture with database master key
 
+> [!NOTE]
+> The instructions in this section are currently applicable to SQL Server 2022 CU18 and later, and SQL Server 2019 CU31 and later. These instructions are not applicable to Azure SQL Managed Instance. 
+
 When using SQL Server authentication for replication, secrets that you provide when you configure replication are stored within SQL Server — specifically, in the distribution database and, for pull subscriptions, also in the subscriber database. 
 
 To enhance the security posture for replication, **before you *start* to configure replication**: 
 
 - Create a [database master key (DMK)](../../../t-sql/statements/create-master-key-transact-sql.md) in the distribution database of the server that hosts the Distributor. 
-- For *pull subscriptions*, also create a DMK in the subscriber database. 
+- For *pull subscriptions*, also create a DMK in the subscriber database.
 
 If replication was created before the DMK, first create the DMK, and then update replication secrets by updating passwords for replication jobs. You can update the job with the same password, or you can use a new password. 
 
@@ -79,7 +82,6 @@ To update replication secrets, use one of the following relevant stored procedur
 - [sp_changedistpublisher](../../system-stored-procedures/sp-changedistpublisher-transact-sql.md)
 - [sp_changepublication_snapshot](../../system-stored-procedures/sp-changepublication-snapshot-transact-sql.md)
 
-
 Configuring transactional replication without a DMK can result in SQL Server warning `14130` on: 
 
 - Azure SQL Managed Instance

docs/relational-databases/system-catalog-views/sys-fulltext-catalogs-transact-sql.md

@@ -36,7 +36,7 @@ dev_langs:
 |data_space_id|**int**|Filegroup where this catalog was created.|  
 |file_id|**int**|File ID of the full-text file associated with the catalog.|  
 |principal_id|**int**|ID of the database principal that owns the full-text catalog.|  
-|is_importing|**bit**|Indicates whether the full-text catalog is being imported:<br /><br /> 1 = The catalog is being imported.<br /><br /> 2 = The catalog is not being imported.|  
+|is_importing|**bit**|Indicates whether the full-text catalog is being imported:<br /><br /> 0 = The catalog is being imported.<br /><br /> 1 = The catalog is not being imported.|  
 
 ## Permissions  
  [!INCLUDE[ssCatViewPerm](../../includes/sscatviewperm-md.md)]  

docs/tools/sqlpackage/media/sqlpackage-with-data-in-parquet-files/data-extract.png

@@ -3,8 +3,8 @@ title: "SqlPackage with Data in Parquet Files (Preview)"
 description: Tips for using SqlPackage with data stored in Azure Blob Storage
 author: dzsquared
 ms.author: drskwier
-ms.reviewer: llali
-ms.date: 10/19/2023
+ms.reviewer: llali, randolphwest
+ms.date: 04/17/2025
 ms.service: sql
 ms.topic: conceptual
 ms.collection:
@@ -17,24 +17,27 @@ ms.custom:
 
 This article covers SqlPackage support for interacting with data stored in Azure Blob Storage that is in Parquet format. For SQL Server 2022 and Azure SQL Managed Instance, preview support for [extract](#extract-export-data) and [publish](#publish-import-data) with data in Parquet files in Azure Blob Storage is available in SqlPackage 162.1.176 and higher. Azure SQL Database and SQL Server 2019 and earlier aren't supported. The [import](sqlpackage-import.md) and [export](sqlpackage-export.md) actions continue to be available for SQL Server, Azure SQL Managed Instance, and Azure SQL Database. Support for Parquet files in Azure Blob Storage continues to be generally available for [Azure Synapse Analytics](sqlpackage-for-azure-synapse-analytics.md).
 
-With [extract](#extract-export-data), the database schema (`.dacpac` file) is written to the local client running SqlPackage and the data is written to Azure Blob Storage in Parquet format. The data is stored in individual folders named with two-part table names. [CETAS](../../t-sql/statements/create-external-table-as-select-transact-sql.md) is used to write the files in Azure Blob Storage.
+With [extract](#extract-export-data), the database schema (`.dacpac` file) is written to the local client running SqlPackage and the data is written to Azure Blob Storage in Parquet format. The data is stored in individual folders named with two-part table names. [CREATE EXTERNAL TABLE AS SELECT (CETAS)](../../t-sql/statements/create-external-table-as-select-transact-sql.md) is used to write the files in Azure Blob Storage.
 
 With [publish](#publish-import-data), the database schema (`.dacpac` file) is read from the local client running SqlPackage and the data is read from or written to Azure Blob Storage in Parquet format.
 
 In SQL databases hosted in Azure, the extract/publish operations with Parquet files offer improved performance over import/export operations with `.bacpac` files in many scenarios.
 
-
 ## Extract (export data)
+
 To export data from a database to Azure Blob Storage, the SqlPackage [extract](sqlpackage-extract.md) action is used with following properties:
-- /p:AzureStorageBlobEndpoint
-- /p:AzureStorageContainer
-- /p:AzureStorageKey or /p:AzureSharedAccessSignatureToken
+
+- `/p:AzureStorageBlobEndpoint`
+- `/p:AzureStorageContainer`
+- `/p:AzureSharedAccessSignatureToken` or `/p:AzureStorageKey` (not supported for use with SQL Server)
+
+:::image type="content" source="media/sqlpackage-with-data-in-parquet-files/data-extract.png" alt-text="Screenshot of Summary of data extract from a database with a .dacpac file written to a SqlPackage environment and the table data written to Azure Blob Storage in parquet files." lightbox="media/sqlpackage-with-data-in-parquet-files/data-extract.png":::
 
 Access for the database to access the blob storage container is authorized via a storage account key. The database schema (.dacpac file) is written to the local client running SqlPackage and the data is written to Azure Blob Storage in Parquet format.
 
 The parameter `/p:AzureStorageRootPath` is optional, which sets the storage root path within the container. Without this property, the path defaults to `servername/databasename/timestamp/`. Data is stored in individual folders named with two-part table names. The number of files created per table depends upon the MAXDOP and available SQL cores at the time of the export.
 
-Finally, the property `/p:TableData` specifies which tables have their data exported. Specify the table name with or without the brackets surrounding the name parts in the format schema_name.table_identifier. This property may be specified multiple times to indicate multiple tables.
+Finally, the property `/p:TableData` specifies which tables have their data exported. Specify the table name with or without the brackets surrounding the name parts in the format schema_name.table_identifier. This property can be specified multiple times to indicate multiple tables.
 
 ### Example
 
@@ -49,10 +52,11 @@ See [SqlPackage extract](sqlpackage-extract.md#examples) for more examples of au
 ## Publish (import data)
 
 To import data from Parquet files in Azure Blob Storage to a database, the SqlPackage [publish](sqlpackage-publish.md) action is used with the following properties:
-- /p:AzureStorageBlobEndpoint
-- /p:AzureStorageContainer
-- /p:AzureStorageRootPath
-- /p:AzureStorageKey or /p:AzureSharedAccessSignatureToken
+
+- `/p:AzureStorageBlobEndpoint`
+- `/p:AzureStorageContainer`
+- `/p:AzureStorageRootPath`
+- `/p:AzureSharedAccessSignatureToken` or `/p:AzureStorageKey` (not supported for use with SQL Server)
 
 Access for publish can be authorized via a storage account key or a shared access signature (SAS) token. The database schema (.dacpac file) is read from the local client running SqlPackage and the data is read from Azure Blob Storage in Parquet format.
 
@@ -66,12 +70,11 @@ SqlPackage /Action:Publish /SourceFile:databaseschema.dacpac /TargetServerName:y
 
 See [SqlPackage publish](sqlpackage-publish.md#examples) for more examples of authentication types available.
 
-
 ## Limitations
 
-### Polybase
+### PolyBase
 
-[Polybase](../../relational-databases/polybase/polybase-guide.md) is required for SqlPackage operations with Parquet files. The following query can be used to check if Polybase is enabled:
+[PolyBase](../../relational-databases/polybase/polybase-guide.md) is required for SqlPackage operations with Parquet files. The following query can be used to check if PolyBase is enabled:
 
 ```sql
 // configuration_id = 16397 is 'allow polybase export'
@@ -80,17 +83,51 @@ SELECT configuration_id, value_in_use FROM sys.configurations
 WHERE configuration_id IN (16397, 16399)
 ```
 
-You may need to enable [Polybase](../../relational-databases/polybase/polybase-installation.md) or [Polybase export](../../database-engine/configure-windows/allow-polybase-export.md). Enabling Polybase on Azure SQL Managed Instance requires [PowerShell or Azure CLI](/sql/t-sql/statements/create-external-table-as-select-transact-sql?view=azuresqldb-mi-current&preserve-view=true#methods-to-enable-cetas). It's recommended that you evaluate whether enabling Polybase is right for your environment before making configuration changes.
+You might need to enable [PolyBase](../../relational-databases/polybase/polybase-installation.md) or [PolyBase export](../../database-engine/configure-windows/allow-polybase-export.md). Enabling PolyBase on Azure SQL Managed Instance requires [PowerShell or Azure CLI](/sql/t-sql/statements/create-external-table-as-select-transact-sql?view=azuresqldb-mi-current&preserve-view=true#methods-to-enable-cetas). You should evaluate whether enabling PolyBase is right for your environment before making configuration changes.
 
 ### Table and data types
 
-Data types supported by [CETAS](../../t-sql/statements/create-external-table-as-select-transact-sql.md#supported-data-types) are supported for extract and publish operations with Parquet files.
+Most data types are supported for extract and publish operations with Parquet files. Tables with unsupported data types result in the table data for that table being exported to the `.dacpac` file instead of in Parquet format. The following data types are supported and are written to Parquet files in Azure Blob Storage:
+
+- **char**
+- **varchar**
+- **nchar**
+- **nvarchar**
+- **text**
+- **ntext**
+- **decimal**
+- **numeric**
+- **float**
+- **real**
+- **bit**
+- **tinyint**
+- **smallint**
+- **int**
+- **bigint**
+- **smallmoney**
+- **money**
+- **smalldate**
+- **smalldatetime**
+- **date**
+- **datetime**
+- **datetime2**
+- **datetimeoffset**
+- **time**
+- **uniqueidentifier**
+- **timestamp**
+- **rowversion**
+- **binary**
+- **varbinary**
+- **image**
+- **xml**
+- **json**
+- **vector**
 
 Ledger tables are enabled for extract and publish operations with Parquet files.
 
 Data stored with Always Encrypted isn't supported for extract and publish operations with Parquet files.
 
-Checking the database for unsupported types is done prior to extract to Parquet by SqlPackage, but you can examine your database quickly with T-SQL. The following sample query returns a result set of types and tables with types not supported for writing to Parquet files.
+You can examine your database with T-SQL to detect data types that would be written into the `.dacpac` file instead of in Parquet files written directly to Azure Blob Storage. The following sample query returns a result set of types and tables with types not supported for writing to Parquet files.
 
 ```sql
 SELECT DISTINCT C.DATA_TYPE, C.TABLE_SCHEMA, C.TABLE_NAME 
@@ -117,22 +154,29 @@ WHERE C.DATA_TYPE NOT IN (
     'numeric',
     'float',
     'real',
-    'bigint',
     'tinyint',
     'smallint',
     'int',
     'bigint',
     'bit',
     'money',
     'smallmoney',
-    'uniqueidentifier'
-)
+    'uniqueidentifier',
+    'timestamp',
+    'rowversion',
+    'text',
+    'ntext',
+    'image',
+    'xml',
+    'json',
+    'vector'
+);
 ```
 
-## Next Steps
+## Related content
 
-- Learn more about [Extract](sqlpackage-extract.md)
-- Learn more about [Publish](sqlpackage-publish.md)
-- Learn more about [Azure Blob Storage](/azure/storage/blobs/storage-blobs-introduction)
-- Learn more about [Azure Storage shared access signature (SAS)](/azure/storage/common/storage-sas-overview)
-- Learn more about [Azure Storage Account Keys](/azure/storage/common/storage-account-keys-manage)
+- [SqlPackage Extract parameters and properties](sqlpackage-extract.md)
+- [SqlPackage Publish parameters, properties, and SQLCMD variables](sqlpackage-publish.md)
+- [Azure Blob Storage](/azure/storage/blobs/storage-blobs-introduction)
+- [Azure Storage shared access signature (SAS)](/azure/storage/common/storage-sas-overview)
+- [Azure Storage Account Keys](/azure/storage/common/storage-account-keys-manage)