MicrosoftDocs
diff --git a/‎azure-sql/database/authentication-azure-ad-user-assigned-managed-identity.md
Lines changed: 6 additions & 2 deletions b/‎azure-sql/database/authentication-azure-ad-user-assigned-managed-identity.md
Lines changed: 6 additions & 2 deletions
diff --git a/‎docs/relational-databases/performance/parameter-sensitive-plan-optimization.md
Lines changed: 2 additions & 2 deletions b/‎docs/relational-databases/performance/parameter-sensitive-plan-optimization.md
Lines changed: 2 additions & 2 deletions
diff --git a/‎docs/relational-databases/system-dynamic-management-views/sys-dm-db-missing-index-group-stats-query-transact-sql.md
Lines changed: 56 additions & 57 deletions b/‎docs/relational-databases/system-dynamic-management-views/sys-dm-db-missing-index-group-stats-query-transact-sql.md
Lines changed: 56 additions & 57 deletions
diff --git a/‎docs/t-sql/queries/hints-transact-sql-query.md
Lines changed: 3 additions & 26 deletions b/‎docs/t-sql/queries/hints-transact-sql-query.md
Lines changed: 3 additions & 26 deletions
diff --git a/‎docs/tools/sqlpackage/release-notes-sqlpackage.md
Lines changed: 47 additions & 1 deletion b/‎docs/tools/sqlpackage/release-notes-sqlpackage.md
Lines changed: 47 additions & 1 deletion
@@ -63,7 +63,9 @@ These permissions should be granted before you provision a logical server or man
 
 ### Permissions for SMI
 
-The same Microsoft Graph applications are needed for the SMI, but the UMI permissions can be eliminated for Azure SQL Database using an SMI. The `CREATE USER` T-SQL syntax would need the `SID` and `TYPE` syntax, as described in the article, [CREATE USER (Transact-SQL)](/sql/t-sql/statements/create-user-transact-sql#syntax).
+The same Microsoft Graph applications permissions are needed with the SMI.
+
+Applies only to **Azure SQL Database**: Using an SMI gives an opportunity to not explicitly provision the Microsoft Graph permissions. The Microsoft Entra users can still be created without the needed Microsoft Graph permission by using the `CREATE USER` T-SQL syntax. This would require the `SID` and `TYPE` syntax, as described in the article, [CREATE USER (Transact-SQL)](/sql/t-sql/statements/create-user-transact-sql#syntax).
 
 ```syntaxsql 
 CREATE USER   
@@ -82,7 +84,9 @@ CREATE USER
     | TYPE = { X | E }
 ```
 
-The above syntax allows creation of Microsoft Entra users without validation. For this to work, the `Object Id` of the Microsoft Entra principal would have to be supplied and used as an `SID` in the T-SQL statement, as explained in [Create a contained database user from a Microsoft Entra principal without validation](/sql/t-sql/statements/create-user-transact-sql#k-create-a-contained-database-user-from-a-microsoft-entra-principal-without-validation).
+The above syntax allows creation of Microsoft Entra users *without validation.* For this to work, the `Object Id` of the Microsoft Entra principal would have to be supplied and used as an `SID` in the T-SQL statement, as explained in [Create a contained database user from a Microsoft Entra principal without validation](/sql/t-sql/statements/create-user-transact-sql#k-create-a-contained-database-user-from-a-microsoft-entra-principal-without-validation).  
+
+The validity check of the **Object Id** is the responsibility of the user running the T-SQL statement.
 
 ### Grant permissions
 
 
@@ -228,7 +228,7 @@ SET QUERY_STORE = ON (
 
 - To disable PSP optimization at the database level, use the `ALTER DATABASE SCOPED CONFIGURATION SET PARAMETER_SENSITIVE_PLAN_OPTIMIZATION = OFF` database scoped configuration.
 
-- To disable PSP optimization at the query level, use the `DISABLE_PARAMETER_SENSITIVE_PLAN_OPTIMIZATION` query hint.
+- To disable PSP optimization at the query level, use the `DISABLE_PARAMETER_SENSITIVE_PLAN` query hint.
 
 - If parameter sniffing is disabled by Trace Flag 4136, `PARAMETER_SNIFFING` database scoped configuration, or the `USE HINT('DISABLE_PARAMETER_SNIFFING')` query hint, PSP optimization is disabled for the associated workloads and execution contexts. For more information, see [Hints (Transact-SQL) - Query](../../t-sql/queries/hints-transact-sql-query.md) and [ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md).
 
@@ -327,7 +327,7 @@ Refer to the [Remarks](how-query-store-collects-data.md#remarks) section of the
 **Workaround**: The query variants that are in the Query Store can be removed, or the PSP feature can be temporarily disabled at the query or database level until additional fixes become available if your system is still experiencing access violations in Query Store with PSP integration enabled after applying Cumulative Update 7 for [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)].
 
 - To disable PSP optimization at the database level, use the `ALTER DATABASE SCOPED CONFIGURATION SET PARAMETER_SENSITIVE_PLAN_OPTIMIZATION = OFF` database scoped configuration.
-- To disable PSP optimization at the query level, use the `DISABLE_PARAMETER_SENSITIVE_PLAN_OPTIMIZATION` query hint.
+- To disable PSP optimization at the query level, use the `DISABLE_PARAMETER_SENSITIVE_PLAN` query hint.
 
 To remove all of the query variants from the Query Store, not just the query variants that appear in the [sys.query_store_query_variant (Transact-SQL)](../system-catalog-views/sys-query-store-query-variant.md#sysquery_store_query_variant-transact-sql) catalog view, a query similar to the following one can be used. Replace `[<database>]` with the appropriate database that was experiencing issues:
 
 
@@ -4,7 +4,7 @@ description: "Query hints specify that the indicated hints are used in the scope
 author: rwestMSFT
 ms.author: randolphwest
 ms.reviewer: wiassaf
-ms.date: 03/26/2025
+ms.date: 04/15/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -106,7 +106,7 @@ Query hints specify that the indicated hints are used in the scope of a query. T
   | QUERYTRACEON <integer_value>
   | RECOMPILE
   | ROBUST PLAN
-  | USE HINT ( <use_hint_name> [ , ...n ] )
+  | USE HINT ( 'hint_name' [ , ...n ] )
   | USE PLAN N'<xml_plan>'
   | TABLE HINT ( <exposed_object_name> [ , <table_hint> [ [ , ] ...n ] ] )
   | FOR TIMESTAMP AS OF '<point_in_time>'
@@ -135,29 +135,6 @@ Query hints specify that the indicated hints are used in the scope of a query. T
   | UPDLOCK
   | XLOCK
 }
-
-<use_hint_name> ::=
-{ 'ASSUME_JOIN_PREDICATE_DEPENDS_ON_FILTERS'
-  | 'ASSUME_MIN_SELECTIVITY_FOR_FILTER_ESTIMATES'
-  | 'ASSUME_FULL_INDEPENDENCE_FOR_FILTER_ESTIMATES'
-  | 'ASSUME_PARTIAL_CORRELATION_FOR_FILTER_ESTIMATES'
-  | 'DISABLE_BATCH_MODE_ADAPTIVE_JOINS'
-  | 'DISABLE_BATCH_MODE_MEMORY_GRANT_FEEDBACK'
-  | 'DISABLE_DEFERRED_COMPILATION_TV'
-  | 'DISABLE_INTERLEAVED_EXECUTION_TVF'
-  | 'DISABLE_OPTIMIZED_NESTED_LOOP'
-  | 'DISABLE_OPTIMIZER_ROWGOAL'
-  | 'DISABLE_PARAMETER_SNIFFING'
-  | 'DISABLE_ROW_MODE_MEMORY_GRANT_FEEDBACK'
-  | 'DISABLE_TSQL_SCALAR_UDF_INLINING'
-  | 'DISALLOW_BATCH_MODE'
-  | 'ENABLE_HIST_AMENDMENT_FOR_ASC_KEYS'
-  | 'ENABLE_QUERY_OPTIMIZER_HOTFIXES'
-  | 'FORCE_DEFAULT_CARDINALITY_ESTIMATION'
-  | 'FORCE_LEGACY_CARDINALITY_ESTIMATION'
-  | 'QUERY_OPTIMIZER_COMPATIBILITY_LEVEL_n'
-  | 'QUERY_PLAN_PROFILE'
-}
 ```
 
 ## Arguments
@@ -344,7 +321,7 @@ If such a plan isn't possible, the Query Optimizer returns an error instead of d
 
 **Applies to**: [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] (starting with [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)] SP1), [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], and [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)].
 
-Provides one or more extra hints to the query processor. The extra hints are specified with a hint name *inside single quotation marks*.
+Provides one or more extra hints to the query processor. The extra hints are specified with the hint name *inside single quotation marks*.
 
 > [!TIP]  
 > Hint names are case-insensitive.
 
@@ -4,7 +4,7 @@ description: Release notes for Microsoft SqlPackage.
 author: dzsquared
 ms.author: drskwier
 ms.reviewer: llali
-ms.date: 02/28/2025
+ms.date: 04/15/2025
 ms.service: sql
 ms.topic: release-notes
 ms.collection:
@@ -18,6 +18,52 @@ ms.custom:
 
 This article lists the features and fixes delivered by the released versions of SqlPackage.
 
+## 170.0.94 SqlPackage
+
+**Release date:** April 15, 2025
+
+```bash
+dotnet tool install -g microsoft.sqlpackage --version 170.0.94
+```
+
+|Platform|Download|
+|:---|:---|
+|Windows .NET 8 |[.zip file](https://go.microsoft.com/fwlink/?linkid=2316204)|
+|Windows|[.msi file](https://go.microsoft.com/fwlink/?linkid=2316310)|
+|macOS .NET 8 |[.zip file](https://go.microsoft.com/fwlink/?linkid=2316113)|
+|Linux .NET 8 |[.zip file](https://go.microsoft.com/fwlink/?linkid=2316311)|
+
+### Features
+
+|Feature|Details|
+|:---|:---|
+| DacpacVerify | Support for verifying the contents of two `.dacpac` files is added in the preview tool [Microsoft.DacpacVerify](https://www.nuget.org/packages/Microsoft.dacpacverify). |
+| Extract | Adds support for unpacking a `.dacpac` file to a folder. The `/Action:Extract` command is used with `/SourceFile:` and `/TargetFile:` parameters. The target file must be a folder and when a source file (`.dacpac`) is specified no database connection properties are valid. The property `/p:ExtractTarget=SchemaObjectType` is required for extracting from a `.dacpac` file instead of a source database. The executable Dacunpack.exe is removed from the DacFx.msi installer. |
+| Parquet | Adds support for the data types timestamp, rowversion, uniqueidentifier, text, ntext, image, json, xml, and vector when using Parquet files in Azure Blob Storage with SqlPackage extract and publish operations. |
+| Parquet | Adds support for exporting and importing table data to bcp files when the table contains an unsupported data type while using Parquet files in Azure Blob Storage for the remaining data with SqlPackage extract and publish operations. An example data type is SQL_VARIANT, and a table containing a column of that type would be written to bcp in the `.dacpac` while the remaining tables would be written to Parquet files in Azure Blob Storage. |
+| Platform | Updated SqlPackage for .NET Framework version to .NET Framework 4.7.2. |
+| Platform | Removed support for .NET 6. |
+| ScriptDom | Updated ScriptDom to version 170.18.0. |
+| SQL projects | The default compatibility level for Azure SQL Database and SQL database in Fabric is now set to 170. |
+| Vector | Vector data type is now supported in the target platform `Azure SQL Database` for import, export, extract, deployment, and SQL project build. |
+
+
+### Fixes
+
+|Feature|Details|
+|:---|:---|
+| Deployment | Fixes an issue where deploying a change to an external table would cause all external tables to be dropped and recreated if the modified table contained no values for REJECT_VALUE or REJECT_SAMPLE_VALUE. |
+| Deployment | Fixes an issue where altering a column to expand its length results in an incorrect data loss warning if the column's collation is specified and matches the database default collation. [GitHub](https://github.com/microsoft/DacFx/issues/453) |
+| Deployment | Fixes an issue where sensitivity classification changes on a table would cause indexes to be recreated. [GitHub](https://github.com/microsoft/DacFx/issues/567) |
+| Export | Optimizes the use of table size estimation during export operations. |
+| Extract | Fixes an issue where extracting a `.dacpac` with a database reference fails. [GitHub](https://github.com/microsoft/DacFx/issues/343) |
+| Fabric Data Warehouse | Fixes an issue where the sp_refreshsqlmodule system stored procedure would be called during a publish operation. Fabric Data Warehouse does not support sp_refreshsqlmodule and this would cause the deployment to fail. |
+| Fabric Data Warehouse | Fixes an issue where table constraints would be included in a `.dacpac` but not `.sql` files when a database was extracted from a Fabric Data Warehouse. [GitHub](https://github.com/microsoft/DacFx/issues/589) |
+| SQL projects | Fixes an issue where building without SSDT installed in Visual Studio results in incorrect build behavior. [GitHub](https://github.com/microsoft/DacFx/issues/99) |
+| SQL projects | Fixes an issue where build warnings are duplicated in output when code analysis is enabled. [GitHub](https://github.com/microsoft/DacFx/issues/481) |
+| SQL projects | Fixes an issue where [service broker](../../database-engine/configure-windows/sql-server-service-broker.md) parameters set to variables results in false warnings. [GitHub](https://github.com/microsoft/DacFx/issues/326) |
+
+
 ## 162.5.57 SqlPackage
 
 **Release date:** November 21, 2024