How To Configure Room Alert Manager To Write To An External Database
By default, Room Alert Manager uses a built-in H2 database to store its configuration settings and historic sensor data; however, if you plan to retain a significant amount of sensor data, it is best to store it to an external database. Room Alert Manager currently support both SQL Server and MySQL. Please note that when you switch to a new database, any sensor data stored in the original database does not get migrated over.
Select the tabs below for instructions to configure Room Alert Manager to work with SQL Server or MySQL.
SQL ServerMySQL
The current version of Room Alert Manager supports SQL Server 2017 and newer.
Step 1: Configure your database in SQL Server.
Configure a new database to store your Room Alert sensor data.
You may use any naming convention you’d like. In our example, we called our database “roomalertmanager.”
Create a schema for your new database. It must be named “room_alert_manager.”
Create a new login. In our example, we called ours “ITMgr.”
For best results, we recommend configuring this user with SQL Server Authentication (as opposed to Windows Authentication.)
This user should be mapped ONLY to the new database that you created.
Assign this user the role of “db owner.”
The screenshot below shows our example Login’s User Mapping Properties.
Step 2: Configure your settings in Room Alert Manager.
Follow the steps below to configure Room Alert Manager to log sensor data to your SQL Server database.