History[04][05][02]

Tibero was first released in June 2003 by TmaxSoft. Tibero 4 was the first version to introduce Tibero Active Cluster (TAC) for distributed database clustering, and this feature has carried onto newer versions since then. Tibero 6, its latest version as of Nov 2019, was released in 2015.

Data Model

Indexes[06][02]

Tibero uses B-Trees to create indexes. It also supports organizing tables with clustered indexes on primary keys. Searching on indexes can be done with single attributes or on a range. An index can be created and searched on composite key from multiple attributes. BitMap Indexing is supported for OLAP data warehouses.

Isolation Levels[07]

Tibero claims to ensure Serializable isolation level

Joins[02]

Parallel Execution[02]

Tibero uses both intra-operator and inter-operator simultaneously for parallel execution. The query coordinator allocates worker threads to perform intra-operator parallelism. The number of worker threads allocated depends on a configurable parameter. These worker threads form a producer set. At the same time, another collection of worker threads called a consumer set is created. The producer set delivers rows to the consumer set to process the next execution plan simultaneously for inter-operator parallelism.

Query Execution[02]

Tibero uses the pipeline model for inter-operator parallelism.

Storage Architecture[08][09][02]

Tibero stores data files on one or more non-volatile storages. However, in 2008 TmaxSoft released its own in-memory DBMS called Tibero MMDB. In 2012, the company has made an interview that it is currently considering amalgamating the original disk-oriented product with its in-memory DBMS in the future.

Storage Model[02]

Tibero stores table rows in a disk block until the block's free space reaches a percentage below a configurable parameter. Large objects are stored in multiple blocks unless the parameter is configured to be sufficiently large.

Storage Organization[02]

At a physical level, Tibero stores a control file that acts as a directory to keep track of all data files in the database. The data files each belong to a tablespace which refers to a specific table/index. At a logical level, data files are organized as a collection of blocks within a tablespace.

Views[02]

Tibero supports virtual views. It uses materialized views to optimize queries.