Merge pull request #13877 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-13 05:00 UTC

Author: learn-build-service-prod[bot]

docs/data-engineering/lakehouse-shortcuts.md

@@ -58,7 +58,7 @@ You can create shortcuts to both internal Fabric items and external storage syst
 - [Amazon S3 compatible storage](../onelake/create-s3-compatible-shortcut.md)
 - [Google Cloud Storage](../onelake/create-gcs-shortcut.md)
 - [Dataverse](../onelake/create-dataverse-shortcut.md)
-- [OneDrive and SharePoint](../onelake/create-onedrive-sharepoint-shortcut.md)
+- [OneDrive and SharePoint](../onelake/shortcuts/create-onedrive-sharepoint-shortcut.md)
 - [On-premises or network-restricted locations](../onelake/create-on-premises-shortcut.md) (through the on-premises data gateway)
 - [Iceberg tables](../onelake/onelake-iceberg-tables.md)
 

docs/data-warehouse/tables.md

@@ -2,7 +2,7 @@
 title: Tables in Fabric Data Warehouse
 description: Learn how to design and use tables in Microsoft Fabric Data Warehouse, including temporary tables.
 ms.reviewer: xiaoyul, randolphwest
-ms.date: 09/24/2025
+ms.date: 04/03/2026
 ms.topic: how-to
 ms.search.form: Warehouse design and development # This article's title should not change. If so, contact engineering.
 ---
@@ -107,7 +107,7 @@ Session-scoped temporary (`#temp`) tables can be created in Fabric Data Warehous
 
 These tables exist only within the session in which they are created and last for the duration of that session. They are not visible to other users or sessions and are automatically dropped from the system once the session ends or the #temp table is dropped. These tables are accessible to all users without requiring specific item-level permission.
 
-Two types of #temp tables can be created based on specific use cases, non-distributed and distributed.
+Two types of #temp tables can be created based on specific use cases: non-distributed and distributed.
 
 - A non-distributed #temp table (mdf-backed) is the default type. The syntax for creating and using non-distributed #temp tables in Fabric Data Warehouse is similar to user tables, but you need to prefix the temp table name with `#`.
 
@@ -129,9 +129,13 @@ Two types of #temp tables can be created based on specific use cases, non-distri
 
 In the previous script, `data_type1` and `data_type2` are placeholders for supported [Data types in Fabric Data Warehouse](data-types.md).
 
-Distributed #temp tables are recommended, as they align with normal user tables; they have unlimited storage, data type support, and T-SQL operations. The syntax for data manipulation and definition is identical to user tables in Fabric Data Warehouse, with prefix `#` added to the table name.
+Distributed #temp tables are recommended, as they align with normal user tables; they have unlimited storage, data type support, and T-SQL operations. 
 
-In Fabric Data Warehouse, temp tables are not affected by [time travel](time-travel.md) query hints and always return the latest data in the table.
+Other notes about temp tables in Fabric Data Warehouse:
+
+- The syntax for data manipulation and definition is identical to user tables in Fabric Data Warehouse, with prefix `#` added to the table name.
+- Temp tables are not affected by [time travel](time-travel.md) query hints and always return the latest data in the table.
+- You can alter distributed temp tables with `ALTER TABLE`, but not MDF-backed temp tables.
 
 ## Align source data with the data warehouse
 

docs/data-warehouse/transactions.md

@@ -2,7 +2,7 @@
 title: Transactions in Fabric Data Warehouse
 description: Learn how to use transactions and how to insert and modify data in Warehouse tables in Microsoft Fabric.
 ms.reviewer: twcyril
-ms.date: 10/17/2025
+ms.date: 4/7/2026
 ms.topic: how-to
 ms.search.form: Warehouse design and development
 ---
@@ -16,7 +16,7 @@ Fabric Data Warehouse supports ACID-compliant transactions. Each transaction is
 
 ## Explicit transactions
 
-You can modify data that is stored in tables in a [!INCLUDE [fabric-dw](includes/fabric-dw.md)] using explicit transactions to group changes together. 
+You can modify data that is stored in tables in a [!INCLUDE [fabric-dw](includes/fabric-dw.md)] using explicit transactions to group changes together.
 
 For example, you could commit inserts to multiples tables, or, none of the tables if an error arises. If you're changing details about a purchase order that affects three tables, you can group those changes into a single transaction. That means when those tables are queried, they either all have the changes or none of them do. Transactions are a common practice for when you need to ensure your data is consistent across multiple tables.
 
@@ -25,6 +25,26 @@ You can use standard T-SQL (`BEGIN TRAN`, `COMMIT TRAN`, and `ROLLBACK TRAN`) sy
     - [COMMIT TRANSACTION](/sql/t-sql/language-elements/commit-transaction-transact-sql?view=fabric&preserve-view=true)
     - [ROLLBACK TRANSACTION](/sql/t-sql/language-elements/rollback-transaction-transact-sql?view=fabric&preserve-view=true)
 
+For example, Fabric Data Warehouse will treat these schema changes as a single atomic unit:
+
+```sql
+-- Sample Syntax--- 
+BEGIN TRAN; 
+ALTER TABLE <table_name> ADD <column_name> <type>; 
+ALTER TABLE <table_name> DROP COLUMN <column_name>; 
+COMMIT; 
+```
+
+If any statement in the transaction fails, all schema changes are automatically rolled back.
+
+Fabric Data Warehouse supports executing the following inside an explicit transaction:  
+
+- `ALTER TABLE` add nullable columns 
+- `ALTER TABLE` drop columns 
+- `ALTER TABLE` add or drop `PRIMARY KEY`, `UNIQUE`, and `FOREIGN KEY` constraints with the `NOT ENFORCED` keyword
+- Multiple `ALTER TABLE` statements
+- `ALTER TABLE` on distributed temporary tables
+
 ### Cross-database query transaction support
 
 [!INCLUDE [fabric-dw](includes/fabric-dw.md)] in [!INCLUDE [product-name](../includes/product-name.md)] supports transactions that span across warehouses that are within the same workspace, including reading from the [SQL analytics endpoint of the Lakehouse](data-warehousing.md#sql-analytics-endpoint-of-the-lakehouse). For an example, see [Write a cross-database SQL Query](query-warehouse.md#write-a-cross-database-query).
@@ -129,7 +149,6 @@ INSERT statements always create new parquet files, which means fewer conflicts w
 ## Limitations
 
 - Distributed transactions are not supported, for example, `BEGIN DISTRIBUTED TRANSACTION`.
-- `ALTER TABLE` is not supported within an explicit transaction.
 - Save points are not supported.
 - Named transactions are not supported.
 - Marked transactions are not supported.

docs/data-warehouse/tsql-surface-area.md

@@ -2,7 +2,7 @@
 title: T-SQL Surface Area in Fabric Data Warehouse
 description: T-SQL surface area of the SQL analytics endpoint and warehouse in Microsoft Fabric.
 ms.reviewer: cynotebo, jovanpop, twinklecyril, emtehran, prlangad
-ms.date: 02/04/2026
+ms.date: 04/07/2026
 ms.topic: concept-article
 ms.search.form: T-SQL Surface area # This article's title should not change. If so, contact engineering.
 ---
@@ -21,28 +21,28 @@ For SQL database in Fabric, see [Limitations in SQL database (preview)](../datab
 
 Fabric Data Warehouse supports T-SQL tables, views, stored procedures, functions, permissions, and security roles. 
 
-- For more about CREATE/DROP TABLE support in [!INCLUDE [fabric-dw](includes/fabric-dw.md)], see [Tables](tables.md).
+- For more about `CREATE`/`DROP` `TABLE` support in [!INCLUDE [fabric-dw](includes/fabric-dw.md)], see [Tables](tables.md).
 - For more about supported data types in [!INCLUDE [fabric-dw](includes/fabric-dw.md)], see [Data types](data-types.md).
 - You can also create T-SQL views, functions, and procedures on top of the tables that reference your Delta Lake data in the [!INCLUDE [fabric-se](includes/fabric-se.md)] of the Lakehouse.
    - Creating, altering, and dropping tables, and insert, update, and delete are only supported in [!INCLUDE [fabric-dw](includes/fabric-dw.md)] in [!INCLUDE [product-name](../includes/product-name.md)], not in the [!INCLUDE [fabric-se](includes/fabric-se.md)] of the Lakehouse.
-- Fabric Warehouse and SQL analytics endpoint both support *standard*, *sequential*, and *nested* CTEs. While CTEs are generally available in Microsoft Fabric, nested CTEs are currently a preview feature. For more information, see [Nested Common Table Expression (CTE) in Fabric data warehousing (Transact-SQL)](/sql/t-sql/queries/nested-common-table-expression?view=fabric&preserve-view=true).
+- Fabric Warehouse and SQL analytics endpoint both support *standard*, *sequential*, and *nested* common table expressions (CTEs). While CTEs are generally available in Microsoft Fabric, nested CTEs are currently a preview feature. For more information, see [Nested Common Table Expression (CTE) in Fabric data warehousing (Transact-SQL)](/sql/t-sql/queries/nested-common-table-expression?view=fabric&preserve-view=true).
 - [TRUNCATE TABLE](/sql/t-sql/statements/truncate-table-transact-sql?view=fabric&preserve-view=true) is supported in [!INCLUDE [fabric-dw](includes/fabric-dw.md)].
 - To change the name of the column in a user table in [!INCLUDE [fabric-dw](includes/fabric-dw.md)], use the `sp_rename` stored procedure. 
 - A subset of query and join hints are supported in [!INCLUDE [fabric-dw](includes/fabric-dw.md)]. For more information, see [Hints (Transact-SQL)](/sql/t-sql/queries/hints-transact-sql-query?view=fabric&preserve-view=true).
 - Session-scoped distributed #temp tables are supported in [!INCLUDE [fabric-dw](includes/fabric-dw.md)] in [!INCLUDE [product-name](../includes/product-name.md)].
+- Currently, only the following subset of `ALTER TABLE` operations in [!INCLUDE [fabric-dw](includes/fabric-dw.md)] in [!INCLUDE [product-name](../includes/product-name.md)] are supported:
+   - You can `ADD` nullable columns of supported column data types.
+   - `DROP COLUMN` is supported.
+   - `ADD` or `DROP` `PRIMARY KEY`, `UNIQUE`, and `FOREIGN_KEY` column constraints are supported, but only if the `NOT ENFORCED` option has been specified. All other `ALTER TABLE` operations are blocked. There are limitations with adding table constraints or columns when using [Source Control with Warehouse](source-control.md#limitations-in-source-control).
+   - `ALTER` distributed temporary tables are supported.
+   - Supported `ALTER TABLE` statements can be executed inside an explicit user-defined transaction in [!INCLUDE [fabric-dw](includes/fabric-dw.md)] in [!INCLUDE [product-name](../includes/product-name.md)].
 - `MERGE` syntax is supported and is a generally available feature. For more information, see [MERGE T-SQL syntax](/sql/t-sql/statements/merge-transact-sql?view=fabric&preserve-view=true).
 - [AI functions (preview)](ai-functions.md) enable advanced text processing without leaving your warehouse.
 
 ### Limitations
 
 At this time, the following list of commands is NOT currently supported. Don't try to use these commands. Even though they might appear to succeed, they could cause issues to your warehouse.
 
-- `ALTER TABLE ADD`/`ALTER`
-    - Currently, only the following subset of `ALTER TABLE` operations in [!INCLUDE [fabric-dw](includes/fabric-dw.md)] in [!INCLUDE [product-name](../includes/product-name.md)] are supported:
-      - ADD nullable columns of supported column data types.
-      - `DROP COLUMN`
-      - ADD or DROP PRIMARY KEY, UNIQUE, and FOREIGN_KEY column constraints, but only if the NOT ENFORCED option has been specified. All other ALTER TABLE operations are blocked.
-      - There are limitations with adding table constraints or columns when using [Source Control with Warehouse](source-control.md#limitations-in-source-control).
 - `BULK LOAD`
 - `CREATE USER`
 - `FOR JSON` must be the last operator in the query, and so is not allowed inside subqueries