Merge pull request #35558 from WilliamDAssafMSFT/20251013-concurrency

20251013 Fabric DW transaction isolation and concurrency additions

Author: v-shils

docs/t-sql/language-elements/begin-distributed-transaction-transact-sql.md

@@ -23,6 +23,7 @@ helpviewer_keywords:
   - "starting transactions"
 dev_langs:
   - "TSQL"
+monikerRange: " =azuresqldb-current || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current"
 ---
 # BEGIN DISTRIBUTED TRANSACTION (Transact-SQL)
 

docs/t-sql/language-elements/begin-transaction-transact-sql.md

@@ -3,7 +3,7 @@ title: "BEGIN TRANSACTION (Transact-SQL)"
 description: Marks the starting point of an explicit, local transaction. Explicit transactions start with the BEGIN TRANSACTION statement and end with the COMMIT or ROLLBACK statement.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 05/10/2024
+ms.date: 10/27/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -40,7 +40,7 @@ Marks the starting point of an explicit, local transaction. Explicit transaction
 
 ## Syntax
 
-Syntax for SQL Server, Azure SQL Database, and Azure SQL Managed Instance.
+Syntax for SQL Server, Azure SQL Database, Fabric SQL database, and Azure SQL Managed Instance.
 
 ```syntaxsql
 BEGIN { TRAN | TRANSACTION }
@@ -50,7 +50,7 @@ BEGIN { TRAN | TRANSACTION }
 [ ; ]
 ```
 
-Syntax for Synapse Data Warehouse in Microsoft Fabric, Azure Synapse Analytics and Analytics Platform System (PDW).
+Syntax for Fabric Data Warehouse, Azure Synapse Analytics, and Analytics Platform System (PDW).
 
 ```syntaxsql
 BEGIN { TRAN | TRANSACTION }
@@ -61,19 +61,19 @@ BEGIN { TRAN | TRANSACTION }
 
 #### *transaction_name*
 
-**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, and Azure SQL Managed Instance
+**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Fabric SQL database, and Azure SQL Managed Instance
 
 The name assigned to the transaction. *transaction_name* must conform to the rules for identifiers, but identifiers longer than 32 characters aren't allowed. Use transaction names only on the outermost pair of nested `BEGIN...COMMIT` or `BEGIN...ROLLBACK` statements. *transaction_name* is always case sensitive, even when the instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] isn't case sensitive.
 
 #### *@tran_name_variable*
 
-**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, and Azure SQL Managed Instance
+**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Fabric SQL database, and Azure SQL Managed Instance
 
 The name of a user-defined variable containing a valid transaction name. The variable must be declared with a **char**, **varchar**, **nchar**, or **nvarchar** data type. If more than 32 characters are passed to the variable, only the first 32 characters are used. The remaining characters are truncated.
 
 #### WITH MARK [ '*description*' ]
 
-**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, and Azure SQL Managed Instance
+**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Fabric SQL database, and Azure SQL Managed Instance
 
 Specifies that the transaction is marked in the log. *description* is a string that describes the mark. A *description* longer than 128 characters is truncated to 128 characters before being stored in the `msdb.dbo.logmarkhistory` table.
 
@@ -147,7 +147,7 @@ Requires membership in the **public** role.
 
 ### A. Use an explicit transaction
 
-**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Azure SQL Managed Instance, [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)], Analytics Platform System (PDW)
+**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Fabric SQL database, Azure SQL Managed Instance, [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)], Analytics Platform System (PDW)
 
 ```sql
 BEGIN TRANSACTION;
@@ -158,7 +158,7 @@ COMMIT;
 
 ### B. Rolling back a transaction
 
-**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Azure SQL Managed Instance, [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)], Analytics Platform System (PDW)
+**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Fabric SQL database, Azure SQL Managed Instance, [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)], Analytics Platform System (PDW)
 
 The following example shows the effect of rolling back a transaction. In this example, the `ROLLBACK` statement rolls back the `INSERT` statement, but the created table still exists.
 
@@ -172,7 +172,7 @@ ROLLBACK;
 
 ### C. Name a transaction
 
-**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Azure SQL Managed Instance
+**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Fabric SQL database, Azure SQL Managed Instance
 
 The following example shows how to name a transaction.
 
@@ -191,7 +191,7 @@ GO
 
 ### D. Mark a transaction
 
-**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Azure SQL Managed Instance
+**Applies to:** [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)] and later versions, Azure SQL Database, Fabric SQL database, Azure SQL Managed Instance
 
 The following example shows how to mark a transaction. The transaction `CandidateDelete` is marked.
 

docs/t-sql/language-elements/commit-transaction-transact-sql.md

@@ -3,7 +3,7 @@ title: "COMMIT TRANSACTION (Transact-SQL)"
 description: This statement marks the end of a successful implicit or explicit transaction.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 04/15/2024
+ms.date: 10/27/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -27,7 +27,7 @@ helpviewer_keywords:
   - "rolling back transactions, COMMIT TRANSACTION"
 dev_langs:
   - "TSQL"
-monikerRange: ">=aps-pdw-2016 || =azuresqldb-current || =azure-sqldw-latest || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current || =fabric"
+monikerRange: ">=aps-pdw-2016 || =azuresqldb-current || =azure-sqldw-latest || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current || =fabric || =fabric-sqldb"
 ---
 # COMMIT TRANSACTION (Transact-SQL)
 
@@ -39,7 +39,7 @@ Marks the end of a successful implicit or explicit transaction. If `@@TRANCOUNT`
 
 ## Syntax
 
-Syntax for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] and [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)].
+Syntax for [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], [!INCLUDE [fabric-sqldb](../../includes/fabric-sqldb.md)].
 
 ```syntaxsql
 COMMIT [ { TRAN | TRANSACTION }
@@ -48,7 +48,7 @@ COMMIT [ { TRAN | TRANSACTION }
 [ ; ]
 ```
 
-Syntax for Synapse Data Warehouse in Microsoft Fabric, Azure Synapse Analytics, and Parallel Data Warehouse Database.
+Syntax for Fabric Data Warehouse, Azure Synapse Analytics, and Parallel Data Warehouse Database.
 
 ```syntaxsql
 COMMIT [ TRAN | TRANSACTION ]
@@ -59,19 +59,19 @@ COMMIT [ TRAN | TRANSACTION ]
 
 #### *transaction_name*
 
-**Applies to:** [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] and [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)]
+**Applies to:** [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], [!INCLUDE [fabric-sqldb](../../includes/fabric-sqldb.md)].
 
 Ignored by the [!INCLUDE [ssDEnoversion](../../includes/ssdenoversion-md.md)]. *transaction_name* specifies a transaction name assigned by a previous `BEGIN TRANSACTION`. *transaction_name*must conform to the rules for identifiers, but can't exceed 32 characters. *transaction_name* indicates to programmers which nested `BEGIN TRANSACTION` the `COMMIT TRANSACTION` is associated with.
 
 #### *@tran_name_variable*
 
-**Applies to:** [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] and [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)]
+**Applies to:** [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], [!INCLUDE [fabric-sqldb](../../includes/fabric-sqldb.md)].
 
 The name of a user-defined variable containing a valid transaction name. The variable must be declared with a char, varchar, nchar, or nvarchar data type. If more than 32 characters are passed to the variable, only 32 characters are used. The remaining characters are truncated.
 
 #### WITH DELAYED_DURABILITY = { OFF | ON }
 
-**Applies to:** [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] and [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)]
+**Applies to:** [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], [!INCLUDE [fabric-sqldb](../../includes/fabric-sqldb.md)].
 
 Option that requests this transaction should be committed with delayed durability. The request is ignored if the database was altered with `DELAYED_DURABILITY = DISABLED` or `DELAYED_DURABILITY = FORCED`. For more information, see [Control Transaction Durability](../../relational-databases/logs/control-transaction-durability.md).
 
@@ -112,7 +112,7 @@ COMMIT TRANSACTION;
 
 ### B. Commit a nested transaction
 
-**Applies to:** [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] and [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)]
+**Applies to:** [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], [!INCLUDE [fabric-sqldb](../../includes/fabric-sqldb.md)].
 
 The following example creates a table, generates three levels of nested transactions, and then commits the nested transaction. Although each `COMMIT TRANSACTION` statement has a *transaction_name* parameter, there's no relationship between the `COMMIT TRANSACTION` and `BEGIN TRANSACTION` statements. The *transaction_name* parameters help the programmer ensure that the correct number of commits are coded to decrement `@@TRANCOUNT` to 0 and so to commit the outer transaction.
 

docs/t-sql/language-elements/rollback-transaction-transact-sql.md

@@ -3,7 +3,7 @@ title: "ROLLBACK TRANSACTION (Transact-SQL)"
 description: This statement rolls back an explicit or implicit transaction to the beginning of the transaction, or to a savepoint inside the transaction.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 04/15/2024
+ms.date: 10/27/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -23,7 +23,7 @@ helpviewer_keywords:
   - "savepoints [SQL Server]"
 dev_langs:
   - "TSQL"
-monikerRange: ">=aps-pdw-2016 || =azuresqldb-current || =azure-sqldw-latest || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current || =fabric"
+monikerRange: ">=aps-pdw-2016 || =azuresqldb-current || =azure-sqldw-latest || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current || =fabric || =fabric-sqldb"
 ---
 # ROLLBACK TRANSACTION (Transact-SQL)
 
@@ -37,7 +37,7 @@ Rolling back a transaction doesn't include changes made to local variables or ta
 
 ## Syntax
 
-Syntax for SQL Server and Azure SQL Database.
+Syntax for SQL Server, Azure SQL Database, and Fabric SQL database.
 
 ```syntaxsql
 ROLLBACK { TRAN | TRANSACTION }
@@ -46,7 +46,7 @@ ROLLBACK { TRAN | TRANSACTION }
 [ ; ]
 ```
 
-Syntax for Synapse Data Warehouse in Microsoft Fabric, Azure Synapse Analytics, and Parallel Data Warehouse Database.
+Syntax for Fabric Data Warehouse, Azure Synapse Analytics, and Parallel Data Warehouse Database.
 
 ```syntaxsql
 ROLLBACK { TRAN | TRANSACTION }