Mimer SQL and Distributed Transactions
Mimer SQL supports distributed transactions based on the XA interface as defined by Open Group and Microsoft's Distributed Transaction Coordinator (DTC) protocol.
This means that Mimer SQL can participate with other XA and DTC enabled systems to process transactions over different platforms and between databases from different vendors.
The use of Distributed Transactions allows access to Mimer SQL database data from a distributed system, such as an application server. Changes to several different Mimer SQL databases can be grouped together in distributed transactions. This allows data changes to be made in either none, or all of the systems accessed by a transaction. In addition, changes in Mimer SQL can be coordinated with changes made in database management systems from other vendors.
How are distributed transactions handled?
Each part of a distributed transaction is handled as a with the following exceptions:
- The transaction is secured to disk during the prepare phase.
- The transaction is tagged with the appropriate transaction ID as decided by the Transaction Manager (TM).
- Recovery is handled as mandated by XA or DTC.
An example of an XA based environment is the integration of Mimer SQL and BEA Tuxedo, where the programmer can write Tuxedo services using Mimer Embedded SQL to access the database.
Of course, J2EE certified application servers can be used with Mimer SQL using the JDBC/Java development environment. An example here is the use of Mimer SQL with IBMs WebSphere Application Server.
Mimer SQL is also suitable for use in Microsofts COM+ and MTS architectures for application development.
Distributed Transactions in Mimer SQL are available from various database APIs such as JDBC, ODBC and Embedded SQL.
By using the Distributed Transaction functionality in Mimer SQL, it is possible to build high performance, scalable, and robust applications with transactions over several Mimer SQL databases or transactions that span other database brands. This allows changes to be made in either all or none of the systems, thereby ensuring the consistency of the data across database servers.
The XA standard specification can be found at Open Group.
Microsofts Component Object Model (COM).
Suns Enterprise Javabeans solution.
Last updated: 2003-09-04