home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.theory
- Path: sparky!uunet!scifi!paladin!beal
- From: beal@paladin.owego.ny.us (Alan Beal)
- Subject: transaction processing - DBMS vs TP monitor
- Message-ID: <714785823.102962@paladin.owego.ny.us>
- Summary: which is best?
- Keywords: TP 2PC
- Organization: The Design Committee
- Distribution: usa
- Date: Tue, 25 Aug 1992 23:37:02 GMT
- Lines: 29
-
- As database products have started to suport two-phase commit, an important
- questions arises as when one should use a DBMS for transaction processing
- and when one should use the facilities provided by OLTP software. Has anyone
- written a paper providing a set of guidelines for this subject? I would
- like to start a discussion of the pros and cons of each approach and
- arrive at a consensus as to when one approach should be used over another.
- It seems that if I want to update multiple heterogeneous databases, then
- OLTP is the way to go now. But with a multiple homongeneous databases,
- using a DBMS to has many benefits including location transparency and
- a simpler interface (SQL statements, then COMMIT). Here are some comparisons
- that come to mind:
-
- DBMS OLTP
- ---------------------------------- ----------------------------------
- Pros Simple SQL interface Heterogeneous DBMS, file support
- Location transparency XA interface supported by vendors
- Possible global optimization Load balancing
- Transparent network support Interface with CICS
-
- Cons Inconsistent gateways More complex interface
- No heterogeneous support Lack of standards
-
- I look forward to your response.
-
-
- --
- Alan Beal
- Internet: beal@paladin.Owego.NY.US
- USENET: {uunet,uunet!bywater!scifi}!paladin!beal
-