Query Interface

SQL Stored Procedures

Apart from supporting most of the standard SQL statements, VoltDB also allows the user to define pre-compiled stored procedures.

Query Compilation

Stored Procedure Compilation

System Architecture

Shared-Nothing

VoltDB runs on a sharded DBMS cluster. Data partitioning and replication is done automatically across the cluster

Data Model

Relational

VoltDB is based on the standard relational model.

Stored Procedures

Supported

The stored procedure in VoltDB allows the user to define a transaction once and to be invoked later with given parameters. Stored procedures are pre-compiled to reduce execution time. Temporary queries are automatically comipled and executed as a stored procedure. VoltDB supports stored procedures written in SQL or Java.

Checkpoints

Non-Blocking Blocking

The snapshot creation could either block all the other transactions or be done in a non-blocking way (e.g. Copy-On-Write).

Storage Model

N-ary Storage Model (Row/Record)

VoltDB is only designed for fast OLTP queries.

Views

Materialized Views

Views in VoltDB are materialized to improve read speed, and all updates to the original table will have a performance impact.

Logging

Command Logging

VoltDB supports transaction-level logging for all the stored procedures that are invoked. By command logging, the amount of memory overhead is minimized since a single stored procedure invocation could contain arbitrary number of SQL statements. Only logs after the latest snapshot are kept, and the logs are flushed to the disk at a regular interval. This feature is only available in the enterprise edition.

Isolation Levels

Serializable

VoltDB supports serializable isolation level with ACID guarantee. The deterministic ordering of transactions is achieved by controllers at each data partition.

Query Execution

Tuple-at-a-Time Model

Storage Architecture

In-Memory

VoltDB is designed to be an in-memory relational DBMS. Its data persistence is achieved by snapshots stored on disk.

Concurrency Control

Deterministic Concurrency Control

VoltDB schedules transactions deterministically on each partition of the data in the cluster. For transactions that span across partitions, a global serial order controller is responsible for determining the execution order. MVCC mode is only used when taking snapshots.