Database

Mango uses two distinct database systems to store its data. The relational SQL database (H2 by default, with MySQL and PostgreSQL as production alternatives) stores system configuration, user accounts, data point definitions, event records, and other structured metadata. The time-series database (the Enterprise NoSQL module or, in newer versions, the TSL module) stores the high-volume historical point values collected from data sources.

This section covers the setup, maintenance, and tuning of both database layers.

• About the H2 Database -- The embedded Java database used by default for relational data storage. Suitable for evaluation and small deployments.
• How to Restore an H2 Database Backup -- Step-by-step instructions for restoring H2 backups through the UI and via the command line.
• Enterprise NoSQL Database -- The high-performance embedded time-series database (IasTSDB) used to store point value history.
• NoSQL Database Performance Tuning -- Tuning the batch write-behind system, purge settings, shard management, and backup configuration.
• Migrating Historical Data to NoSQL -- How to migrate point value history from H2, MySQL, or Derby into the NoSQL time-series store.
• Database Conversions -- Converting between relational database engines (H2 to MySQL, Derby to H2, etc.).
• Using the SQL Console -- The built-in SQL console for running queries directly against the Mango relational database.
• Persistent Point Value Cache -- Storing cached point values on disk for faster data source startup times.