Technical Documentation
IN THIS ARTICLE

SQL Server Requirements and Database Maintenance

Incorrect email!

The article was successfully sent to the email

Perform all restoration and merging procedures on a separate workstation, and always work only with copies of database backups.

This article provides general recommendations for SQL Server selection, database maintenance, archiving, and handling historical data in TRBOnet systems.

MS SQL Server Compatibility

Use the table below to determine the correct SQL Server version for your TRBOnet release:

Product Version SQL Server
Enterprise / Plus 6.0 and newer 2016 and newer
Enterprise / Plus before 6.0 2008 R2 and newer
Watch 4.0 and newer 2016 and newer
Watch before 4.0 2008 R2 and newer

SQL Express Database Storage and Maintenance

When using SQL Express, proper database maintenance is mandatory due to the 10 GB size limit.

When the database reaches this limit:

  • new records will not be saved,
  • old data cannot be deleted,
  • scheduled backups may fail,
  • the system may become unstable or stop functioning properly.

Regular cleanup is essential.

Store 3 to 12 months of operational data in the active database. Older data should be:

1. archived using the built-in Scheduler,
2. removed from the live database after the backup is created.
Refer to the current TRBOnet User Manual, Appendix D: Backing up and Restoring Database and Audio Recordings.

This prevents uncontrolled database growth.

Upgrading the Database on SQL Express

Database upgrades typically increase size by 20–30% due to schema changes. If the database is already near 8 GB, the upgrade may:

  • fail due to size constraints;
  • corrupt the database and require manual recovery.

Before upgrading:

  • remove old data to reduce database size;
  • ensure sufficient free disk space for the upgrade process.

Database Archive Storage

We recommend storing database and audio backups on a separate data drive (e.g., D:). If the system drive (usually C:) runs out of space, the TRBOnet configuration file may become corrupted, which can result in loss of server settings.

Database archives created by the Scheduler remain on disk until removed manually or by external tools.

To prevent disk depletion:

  • automate archive removal using Windows Task Scheduler or third-party cleanup tools;
  • plan retention based on disk capacity, backup frequency, and audit requirements.

For step-by-step cleanup instructions, see the article.

Accessing Historical Database Archives

To avoid impacting live TRBOnet operations, archived databases should be restored and viewed on a separate PC. If TRBOnet has never been installed on that machine before, you can use it during the 60-day trial period. Alternatively, you may contact us and we will provide a free license for viewing reports.

1. Install the same TRBOnet version as on the production server (Server + Console).
2. Install the same SQL Server version as on the production server.
3. Copy the required database backup files to this standalone machine.
4. Create a new empty database in SQL Server Management Studio (SSMS).
5. Restore the backup(s) into this new database.
6. Configure TRBOnet Server to connect to the restored DB and start the service.
7. Use the TRBOnet Console to generate reports and review historical data.

This method provides full access to archived history without disrupting the production system.

Retrieving Historical Data from Multiple Backups

If long-term history is distributed across several backup files, you can retrieve it using one of two approaches.

Option 1: Restore Backups Sequentially

Restore each backup one at a time on the separate workstation and generate reports after each restore.

Option 2: Merge All Backups Into a Single Database

1. On a separate PC, install the same versions of TRBOnet and SQL Server as the production system.
2. Copy all backup files to this PC.
3. Create a new empty database in SSMS.
4. Restore all backup files into that database (sequential merge).
If the resulting DB exceeds 10 GB, a full SQL Server edition (not SQL Express) will be required.
5. Connect TRBOnet Server to the merged DB.
6. Open TRBOnet Console and run reports on the full, merged history.

SQL Server Requirements and Database Maintenance

Perform all restoration and merging procedures on a separate workstation, and always work only with copies of database backups.

This article provides general recommendations for SQL Server selection, database maintenance, archiving, and handling historical data in TRBOnet systems.

MS SQL Server Compatibility

Use the table below to determine the correct SQL Server version for your TRBOnet release:

Product Version SQL Server
Enterprise / Plus 6.0 and newer 2016 and newer
Enterprise / Plus before 6.0 2008 R2 and newer
Watch 4.0 and newer 2016 and newer
Watch before 4.0 2008 R2 and newer

SQL Express Database Storage and Maintenance

When using SQL Express, proper database maintenance is mandatory due to the 10 GB size limit.

When the database reaches this limit:

  • new records will not be saved,
  • old data cannot be deleted,
  • scheduled backups may fail,
  • the system may become unstable or stop functioning properly.

Regular cleanup is essential.

Store 3 to 12 months of operational data in the active database. Older data should be:

1. archived using the built-in Scheduler,
2. removed from the live database after the backup is created.
Refer to the current TRBOnet User Manual, Appendix D: Backing up and Restoring Database and Audio Recordings.

This prevents uncontrolled database growth.

Upgrading the Database on SQL Express

Database upgrades typically increase size by 20–30% due to schema changes. If the database is already near 8 GB, the upgrade may:

  • fail due to size constraints;
  • corrupt the database and require manual recovery.

Before upgrading:

  • remove old data to reduce database size;
  • ensure sufficient free disk space for the upgrade process.

Database Archive Storage

We recommend storing database and audio backups on a separate data drive (e.g., D:). If the system drive (usually C:) runs out of space, the TRBOnet configuration file may become corrupted, which can result in loss of server settings.

Database archives created by the Scheduler remain on disk until removed manually or by external tools.

To prevent disk depletion:

  • automate archive removal using Windows Task Scheduler or third-party cleanup tools;
  • plan retention based on disk capacity, backup frequency, and audit requirements.

For step-by-step cleanup instructions, see the article.

Accessing Historical Database Archives

To avoid impacting live TRBOnet operations, archived databases should be restored and viewed on a separate PC. If TRBOnet has never been installed on that machine before, you can use it during the 60-day trial period. Alternatively, you may contact us and we will provide a free license for viewing reports.

1. Install the same TRBOnet version as on the production server (Server + Console).
2. Install the same SQL Server version as on the production server.
3. Copy the required database backup files to this standalone machine.
4. Create a new empty database in SQL Server Management Studio (SSMS).
5. Restore the backup(s) into this new database.
6. Configure TRBOnet Server to connect to the restored DB and start the service.
7. Use the TRBOnet Console to generate reports and review historical data.

This method provides full access to archived history without disrupting the production system.

Retrieving Historical Data from Multiple Backups

If long-term history is distributed across several backup files, you can retrieve it using one of two approaches.

Option 1: Restore Backups Sequentially

Restore each backup one at a time on the separate workstation and generate reports after each restore.

Option 2: Merge All Backups Into a Single Database

1. On a separate PC, install the same versions of TRBOnet and SQL Server as the production system.
2. Copy all backup files to this PC.
3. Create a new empty database in SSMS.
4. Restore all backup files into that database (sequential merge).
If the resulting DB exceeds 10 GB, a full SQL Server edition (not SQL Express) will be required.
5. Connect TRBOnet Server to the merged DB.
6. Open TRBOnet Console and run reports on the full, merged history.

Helpful?
We're glad this article helped.

Thanks for letting us know. What went wrong?