Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# SQL Server Transaction Scope

When using the iProcess Suite with the Microsoft SQL Server, all transactions are managed by the SQL Server resource manager. SQL Server provides the following transaction functionality:

| • | Locking facilities that ensure transactional integrity.

| • | Logging facilities that ensure transaction durability. For example, if the hardware, operating system, or SQL Server fails, SQL Server uses the transaction logs, on restart, to automatically roll back any incomplete transactions to the point of the system failure.

| • | Transaction management features that enforce transaction atomicity and consistency. After a transaction has started, it must be successfully completed, or SQL Server undoes all of the data modifications made since the transaction started. See the SQL Server documentation for more information about how SQL Server transactions work.

When all the processes use the local resource manager on the SQL Server, this is called a local transaction. If some processes use an external resource manager such as the EAI COM step, then this is known as a distributed transaction because more than one resource manager is used. A slightly different architecture is used for distributed transactions because a transaction manager program is used to control the resource managers. For more information, see the Using Distributed Transactions with MSDTC.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2024. Cloud Software Group, Inc. All Rights Reserved.