This article applies as of PRTG 26
| Note: This change only affects users who activated PRTG Database. |
New schema for PRTG Database
We released PRTG Database as an optional beta feature with PRTG 26.1.118. With PRTG 26.2.120, we determined that a schema update was necessary to improve the functionality of PRTG.
Why it matters
Database schemas control how data is organized in a database. Changing a schema, such as introducing new database structures, reorganizes how data is stored. Because of this, the original formatting of the data becomes incompatible with the new format, and existing data is often overwritten or lost.
If you activated PRTG Database, PRTG saved your configuration data to the new PostgreSQL database that PRTG Database uses. The PRTG configuration data controls your monitoring setup, for example, the devices, groups, and sensors that make up the device tree or custom reports and libraries.
If you update to PRTG 26.2.120 directly, this configuration data is overwritten by the new schema.
How to update
In order to prevent unintentional deletion of data, we made it impossible to automatically update to a new version of PRTG if you have existing data in the PostgreSQL database. Instead, the update fails and prompts you to contact the Paessler support team. The Paessler support team will work with you to find the best way forward based on your database usage and PRTG configuration.
If your PRTG update fails because of existing data in your database, reach us through the PRTG Helpdesk. You can create a ticket to get into direct contact with the Paessler support team.
