Documentation
Getting Started
Data Grid
Modeling
Business Rules
Approvals
Users, Roles & Security
Administration
Integration & API
Installation
Migrating from MDS
Architecture
Upgrading
Upgrading replaces the application files and then updates the database schema. Your data stays where it is.
Before you start
Take a full database backup. If Primentra runs on a virtual machine, take a snapshot of the server as well. The snapshot also captures the application files, mds-config.json and the Windows service configuration. A database backup alone does not restore those.
Licence keys changed in 1.2026.7.28. Keys are now signed with Ed25519 and are considerably longer. A key issued for an older version stops validating after the upgrade, and the application falls back to read-only. Request a replacement key before you upgrade a licensed installation. See Licensing.
Upgrade steps
- Back up the database, and snapshot the server if it is virtual.
- Download
Primentra-Setup-vX.X.X.exefrom primentra.com. - Run the installer as Administrator. It detects the existing installation, stops the service, replaces the application files, and starts the service again. Your port is read back from the registry.
- Open the application. Primentra compares the application version with the database schema version and shows an Upgrade database schema screen.
- Click Upgrade database, then Continue.
- Create an extra administrator account, or click Skip — use existing account to sign in with the one you have.
- Check the version in the status bar and confirm the database connection is healthy.
Only an administrator can deploy the new schema. Other users see a "Database upgrade required" screen and are asked to wait.
Which database is updated
The one recorded in mds-config.json in the installation folder — the same connection the application uses. The installer never replaces or removes that file, so a database name you chose yourself survives every upgrade. To confirm beforehand, open Settings › General Settings › Connection.
Why the schema update is safe
- Stored procedures use
CREATE OR ALTER, so they are always replaced with the current version. - Migrations are guarded with existence checks. Only new changes are applied.
- The schema script never modifies or deletes your data.
After the upgrade
- Confirm
schemaVersionandappVersionmatch — see Health & Monitoring. - Confirm the licence is still accepted under General Settings › License.
- Check that the
Primentra_SchedulerSQL Agent job still runs.
Related
- Licensing — the Ed25519 key format and how to get a replacement
- Health & Monitoring — verify the schema version after upgrading
- Install Primentra — the first installation
- Troubleshooting — locked files and service errors