In the automation arena real-time operations require fast data collections and
extremely large storage space. Frequently Relational database is compared to
time series data storage historian in such applications. However, a relational
database is built to manage relationships and is not optimized for time-series data.
vM historian offers several advantage of relational database:
Transactionality – vM Historian offers atomicity, consistency and durability with guaranteed integrity and no size limitation. Commit is immediate with no penalty
for large transactions.
Speed - performance is a blazing at 100,000 transactions per second.
Data Compression- continuous, dynamic data compression packs data into
variable-length blocks, avoiding almost all wasted space in internal fragmentation,
while reducing required disk I/O bandwidth. Making blocks variable-length allows
further compression by layering ZLib over UTF-8, with a tripling of storage density common. By providing 100% variable-length data items, compact common data
values, prefix compression plus branch-cell suffix compression, only the required
part of the data is actually stored. Variable-length data items, prefix and
branch-cell suffix compression are used in the memory cache as well. Any size
database benefits from the compression, from 10KB to 10GB and beyond.
Small Footprint – The core engine requires only 2 MB of disk space and no
external DLL or libraries needed. Single database file is ideal for maintenance and backup.
Flexible Data Model – All primitive data type are supported as well as String,
Date, byte and huge arrays of anything and even byte strings. Keys may be
composite or even heterogeneous. Values may be composite, heterogeneous,
unlimited-cardinality multi-valued, or unlimited-length Character- or Binary Long
Objects.
Zero Maintenance - No special setup tasks, No tuning, space allocation, or
resource monitoring, No configuration file, no temporary files, No Logs, No
rollbacks and No corrupted data.
extremely large storage space. Frequently Relational database is compared to
time series data storage historian in such applications. However, a relational
database is built to manage relationships and is not optimized for time-series data.
vM historian offers several advantage of relational database:
Transactionality – vM Historian offers atomicity, consistency and durability with guaranteed integrity and no size limitation. Commit is immediate with no penalty
for large transactions.
Speed - performance is a blazing at 100,000 transactions per second.
Data Compression- continuous, dynamic data compression packs data into
variable-length blocks, avoiding almost all wasted space in internal fragmentation,
while reducing required disk I/O bandwidth. Making blocks variable-length allows
further compression by layering ZLib over UTF-8, with a tripling of storage density common. By providing 100% variable-length data items, compact common data
values, prefix compression plus branch-cell suffix compression, only the required
part of the data is actually stored. Variable-length data items, prefix and
branch-cell suffix compression are used in the memory cache as well. Any size
database benefits from the compression, from 10KB to 10GB and beyond.
Small Footprint – The core engine requires only 2 MB of disk space and no
external DLL or libraries needed. Single database file is ideal for maintenance and backup.
Flexible Data Model – All primitive data type are supported as well as String,
Date, byte and huge arrays of anything and even byte strings. Keys may be
composite or even heterogeneous. Values may be composite, heterogeneous,
unlimited-cardinality multi-valued, or unlimited-length Character- or Binary Long
Objects.
Zero Maintenance - No special setup tasks, No tuning, space allocation, or
resource monitoring, No configuration file, no temporary files, No Logs, No
rollbacks and No corrupted data.