| Transbase | |
|---|---|
| Developer | Transaction Software GmbH |
| Initial release | 1987 (1987)[1] |
| Stable release | |
| Written in | C,Java,.Net |
| Operating system | UNIX,Linux,Windows,Mac OS,iOS,Raspberry Pi OS,Embedded Linux,Android |
| Available in | English |
| Type | RDBMS |
| License | proprietary, evaluation license free |
| Website | www.transaction.de |
Transbase is arelational database management system, developed and maintained byTransaction Software GmbH,Munich. The development of Transbase was started in the 1980s byRudolf Bayer under the name "Merkur" at the department of Computer Science of theTechnical University of Munich (TUM).[1]
Transbase largely conforms with theSQL standard "SQL2 intermediate level" (SQL-92) and supports various features of SQL2 follow-on versions (SQL:1999,SQL:2003 etc.).[2]
As a professor of the computer science department of theTechnical University of Munich,Rudolf Bayerdeveloped adatabase management system called "Merkur" in the 1980s. The development involved a larger number of diploma and PHD students and resulted in 1987 in a new company, calledTransaction Software GmbH, founded by Rudolf Bayer and several co-workers of his institute at TUM. In 1989 "Merkur" was renamed and called "Transbase". The wide use of Transbase, especially as basis for repair part management and documentation systems in the automobile industry soon led to a considerable number of ports to diverse operating systems, such asUNIX derivatives,Linux,Windows,VMS, andMac OS. Major steps in the further development of Transbase were the integration of functions for distributed queries to several databases in parallel, the fulltext-search extension and the support of foreign languages, ("Myriad"[3]) such as Chinese and Japanese,as well as the support of data warehouse functions ("Transbase Hypercube"[4]) and the dynamic, parallel execution of queries.[5]
Transbase supports all important functions of theSQL standard:[2]
The database is extensible via additional functions and custom data types.
The TransbaseCD database option can use read-only storage media such asCD,DVD orBlu-ray Discs. In addition, a persistent disk cache can be utilized to store data for performance improvement and/or for updates of data supplied originally as read-only media. Optionally, TransbaseCD pages can be compressed. This saves half of storage requirement and response times, typically.
Transbase Hypercube supportsRelational Online Analytical Processing (ROLAP), which is primarily used in data warehouse applications. The search function for OLAP data cubes („hyper cubes“) is accelerated dramatically through the use of UB-Trees (in comparison to queries using standard indices).
Transbase offers optional encryption of data stored on disk, using theAdvanced Encryption Standard algorithm, as well as encryption of data transferred through database connections.
Transbase provides parallel execution of queries via dynamicmultithreading technology. This feature executes parts of the query tree in separate threads or splits query sequences into separate threads.
Transbase supportsreplication of a master database in several slave database instances. Replication can be configured synchronous (for hot-standby databases) or asynchronous for distributing database changes to a huge number of recipients. Replicated databases can even be cascaded in the latter case.
Transbase Crowd was designed to store IoT data in local edge databases that are connected to a Transbase Crowd database that distributed query processing automatically over all connected edge databases and thus produces global results. Edge resources are perfectly utilised and data transfer is minimized. This database architecture provides perfect scalability for rapidly growing numbers of IoT devices.
The following summarizes the current limits as implemented in version 6.9 of Transbase: