H2 (DBMS)

From Wikipedia, the free encyclopedia
Jump to: navigation, search
H2 Database Engine
H2 Database Engine
Stable release 1.3.176 / April 5, 2014 (2014-04-05)
Written in Java
Operating system Cross-platform
Type Relational Database Management System
License Eclipse Public License or a modified version of Mozilla Public License 1.1
Website http://www.h2database.com/

H2 is a relational database management system written in Java. It can be embedded in Java applications or run in the client-server mode.[1] The disk footprint (size of the jar file) is about 1.5 MB.[2]

The software is available as open source software under modified versions of the Mozilla Public License or the original Eclipse Public License. The modification of the MPL is a shorter file header and the license name.[3]

Main features[edit]

A subset of the SQL (Structured Query Language) standard[which?] is supported. The main programming APIs are SQL and JDBC, however the database also supports using the PostgreSQL ODBC driver by acting like a PostgreSQL server.[4]

It is possible to create both in-memory tables, as well as disk-based tables. Tables can be persistent or temporary. Index types are hash table and tree for in-memory tables, and b-tree for disk-based tables. All data manipulation operations are transactional. Table level locking and multiversion concurrency control are implemented. The 2-phase commit protocol is supported as well, but no standard API for distributed transactions is implemented. The security features of the database are: role based access rights, encryption of the password using SHA-256 and data using the AES or the Tiny Encryption Algorithm, XTEA. The cryptographic features are available as functions inside the database as well. SSL / TLS connections are supported in the client-server mode, as well as when using the console application.

Two full text search implementations are included, a native implementation and one using Lucene.

A simple form of high availability is implemented: when used in the client-server mode, the database engine supports hot failover (this is commonly known as clustering). However, the clustering mode must be enabled manually after a failure.[5]

The database supports protection against SQL injection by enforcing the use of parameterized statements. In H2, this feature is called 'disabling literals'.[6]

Since version 1.1.111, H2 in-memory database can run inside the Google App Engine.[7]

Durability problems[edit]

H2 documentation describes[8] problems with durability (part of ACID), which can cause data loss of committed transactions in case of a power failure. According to the documentation these problems are not limited to H2, but are also found in some other relational databases.

According to documentation, the system doesn't call FileDescriptor.sync() nor FileChannel.force() nor fsync for every commit because they significantly degrade system performance: only about 100 write operations per second would be achievable when using spinning disks.

Another reason for not using fsync is that many HDD have write caching enabled by factory default.

According to the H2 documentation, such a problem is related not only to the DB engine design, but also to the enabled storage caching mechanism. As storage devices use write cache in order to increase speed, in a situation of power failure, data in the device's cache are lost. Administrators have then to assess the common trade off between speed and data loss risks in the context of the business requirements. Either one forces the storage to write cache frequently or even immediately using fsync and slows the writing process or one accepts caching in the device buffer and risk data loss in case of power failure.

From the HSQLDB documentation: "To avoid this, you can set write delay down to 10 milliseconds. In practice, a write delay of 100 milliseconds provides better than 99.9999% reliability with an average one system crash per day, or 99.99999% with an average one system crash per 6 days."[9]

The documentation advises to use the additional commands SET WRITE_DELAY and CHECKPOINT SYNC to ensure durability. These commands are available to administrators only.

Utilities[edit]

An embedded web server with a browser based console application is included, as well as command line tools to start and stop a server, backup and restore databases, and a command line shell tool.

History[edit]

The development of the H2 database engine started in May 2004, and first published in December 2005. The database engine was written by Thomas Mueller. He also developed the Java database engine Hypersonic SQL.[10] In 2001, the Hypersonic SQL project was stopped, and the HSQLDB Group was formed to continue work on the Hypersonic SQL code. The name H2 stands for Hypersonic 2, however H2 does not share code with Hypersonic SQL or HSQLDB. H2 is built from scratch.[11]

See also[edit]

References[edit]

External links[edit]