Database

   Print  Previous  Next
Overview
Introduction
PostgreSQL Server
SQLite File
SQLite In Main Memory
Notes
Storage Space And Memory Requirements

 

 

Overview

Database options include settings regarding database usage and recorded RDM data.

Go to the menu Preferences > Options... > Database
[Keyboard shortcut: Ctrl + Alt + O > Database]

Start Options

Set up the options as explained below.
Restore the default settings via Defaults.
Confirm any changes with OK or Apply. Discard any changes via Cancel.

 

 

Introduction

Database Management System

You can choose from 3 different Types:

SQLite In Main Memory
[The default option is SQLite In Main Memory.]
SQLite File
PostgreSQL Server

 

Please note: Choosing a different database management system is subject to availability here in the software. A different database system that is not provided as an option cannot be selected or chosen.

 

Comparison

SQLite In Main Memory

SQLite File

PostgreSQL Server

 

 

Is required when using the Big Data/History feature and data trends.
Is useful for short-term monitoring and when data does need not be saved and can thus be discarded without ramifications.
Is useful when using MADRIX RADAR only as configuration tool for device addressing, for example.
Is useful for short-term monitoring and the requirement to have data stored beyond any restart of the software.
Is useful when using MADRIX RADAR only as configuration tool for device addressing, for example.

 

Is the default option.
Does not require any configuration.
Only stores fixture data in the temporary memory of the computer [RAM].
Data quantities are thus limited to the available system memory.
Data can thus be processed and accessed very quickly.
Any data is discarded if the software is closed in any way.
Only requires very little configuration.
Writes a separate file onto the hard drive in order capture, save, and preserve recorded fixture data.
Is an advanced system for data management, which ensures data integrity and data consistency, for example.
Data quantities are thus limited to the available hard-drive space.
Data thus cannot be processed and accessed as quickly as when stored in the system's memory.
Always overwrites parameter values and sensor data with updated information and thus does not enable data trends [that is, no data history is available].
The data is still available even if the software is closed.
Is a sophisticated database system to capture, save, and preserve recorded device data.
Is an advanced system for data management, which ensures data integrity and data consistency, for example.
The data is still available even if the software is closed.
Is automatically provided together with the software's installation.
Is automatically provided together with the software's installation.
Is not included in the software's installation and needs to be installed separately.
A database needs to be created in PSQL after the installation.
[The correct name of the database, login information, and more needs to be set in the options as explained below. See: Options]

 

Switching Databases

When switching to a different option, you will be asked if you would like to scan for devices in the network again.
Please note: Each database holds their own devices. When switching databases, data will not be transferred from the previous database to the new database.

 

 

PostgreSQL Server

Overview

PostgreSQL Server is required when using the Big Data/History feature.

 

Installation

Please Note: This type of database is not automatically installed together with MADRIX RADAR!

 

You need to install this server-based database separately if you wish to use it.
It needs to be installed on the same computer system.

 
Please see the following link for more information:
»https://www.postgresql.org/

 

Options

Driver Directory - Defines the location of the required library file [*.dll] on your computer.
- Browse... - Allows you to choose a different folder or directory.
- Please search for the correct directory on your computer or enter it manually. Usually, the directory is within the PSQL installation folder: <PSQL Installation Directory>\11\bin
- Changing the library path requires a software restart in order to load the required files.
 
Port - Defines the port that is used to establish the connection to the database. This option is available here since the port can be changed in the configuration of PSQL.
[The default value is the PSQL default port 5432.]
 
Database Name - Defines the name of the database. This can be especially useful when managing several projects/databases and the need to distinguish between them.
- Enter the name as defined by you during the creation of a corresponding database in PSQL.
[The default value is MadrixRadarData.]
 
User Name - Enter the name that is used to establish the connection to the database.
[Any input will be saved and encrypted with the Advanced Encryption Standard AES 256.]
 
Password - Enter the password that corresponds with the user name. Any input will be hidden.
[Any input will be saved and encrypted with the Advanced Encryption Standard AES 256.]

 

 

SQLite File

Overview

SQLite can be used to create a separate database file.

 

Options

Data File - Defines the location of the database file on your computer.
- Browse... - Allows you to choose a different folder or directory.
- By default, <User Directory>\Documents\MADRIX RADAR\MadrixRadarData.sqlite is selected.

 

 

SQLite In Main Memory

Overview

SQLite can be used to record only temporary data within the computer's memory.

 

Options

It is not necessary to set up any options for this type of database management system.

 

 

Notes

All RDM database options will be saved locally on your computer.

 

 

Storage Space And Memory Requirements

Overview

Since MADRIX RADAR uses database management systems to manage the data that is accumulated when working with RDM devices, a lot of data might ultimately be handled.
The following examples try to estimate the required storage space for different scenarios.

 

Influencing Factors

Please note: A definite answer cannot be provided, since the needed storage or memory depends on a lot factors.
Such factors are amongst others:

Which database management system is used,
How many RDM devices should be managed,
How many RDM nodes are used,
How many parameters and sensors a device provides/reports,
How often data and status updates are queried from devices,
How many status messages or events may occur during the monitored period of time,
If the data should be recorded or not [Big Data/data history],
And more.

 

Examples

As you will see, using the Big Data features and a PSQL database can result in substantial amounts of data over time.
 
Example 01:
- 1000 RDM devices, with 25 parameters each, with 25 sensors each, are recorded for 1 month [data history] into a PSQL database, while data is queried once per day and each sensor value creates an event.
- Estimation for needed storage/memory : ~100 MB
 
Example 02:
- 200 RDM devices, which support nearly all parameters each, with 50 sensors each, are recorded for 1 day [data history] into a PSQL database, while data is queried every 5 minutes.
- Estimation for needed storage/memory : ~345 MB

 

Example 03:
- 2000 RDM devices, which support MIN/MAX values as well as recorded values, with 20 sensors each, are recorded for 6 months [data history] into a PSQL database, while data is queried every 4 hours.
- Estimation for needed storage/memory : ~5.2 GB
 
Example 04:
- 200 RDM devices, with 50 parameters each, with 50 sensors each, managed with SQLite (file) without data history.
- Estimation for needed storage/memory : 2 MB
 
Example 05:
- 2000 RDM devices, with 10 parameters each, with 10 sensors each, managed with SQLite (in-memory) without data history.
- Estimation for needed storage/memory : 4 MB

 

MADRIX RADAR 1.0.
[Ctrl & +/-] = Zoom In/Out | [Ctrl & 0] = 100%
Print   Previous   Next


Enable automatic translation | Activer la traduction automatique | 启用自动翻译