Skip to content

Commit 92201d1

Browse files
authored
Update to Scope of a Transaction paragraph
Blended feedback from customer per https://github.com/MicrosoftDocs/azure-docs/issues/50152 with the existing information to make the paragraph read more concisely.
1 parent d286d52 commit 92201d1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/stored-procedures-triggers-udfs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ In Azure Cosmos DB, JavaScript runtime is hosted inside the database engine. Hen
5151

5252
### Scope of a transaction
5353

54-
If a stored procedure is associated with an Azure Cosmos container, then the stored procedure is executed in the transaction scope of a logical partition key. Each stored procedure execution must include a logical partition key value that corresponds to the scope of the transaction. For more information, see [Azure Cosmos DB partitioning](partition-data.md) article.
54+
Stored procedures are associated with exactly one Azure Cosmos container and are therfore scoped to exactly one logical partition key. Each stored procedure execution must include a logical partition key value that corresponds to the scope of the transaction. Items that have a different partition key value (and items in different containers) will not be visible to the stored procedure. No mechanism currently exists to perform cross-partition (or cross-container) transactions. For more information, see [Azure Cosmos DB partitioning](partition-data.md) article.
5555

5656
### Commit and rollback
5757

0 commit comments

Comments
 (0)