Moving or Upgrading the adTempus Database
adTempus ships with SQL Server Express 2025 and uses that database by default. However, adTempus is compatible with all versions of SQL Server going back to 2012. (It is tested up to version 2025 and does not use any database features that would be affected by changes in future versions).
You can upgrade the database server used by adTempus at any time, or move the database to a different server, independently of upgrading adTempus.
Stop the adTempus service before upgrading the database server or moving the database, and restart it when the upgrade is complete.
Database Server Upgrade
No changes to adTempus configuration are needed are required when upgrading the database server.
- Standalone SQL Server. If adTempus uses your own SQL Server instance, you or your database administrator can upgrade it. As long as the upgrade does not change the name or address of the database server or the login used by adTempus, no changes are needed.
- SQL Server Express. The version of SQL Server Express included with adTempus may not be the latest version. To use a newer version, download it from Microsoft and run its installer, choose the option to upgrade an existing instance, select the "ADTEMPUS" instance, and complete the upgrade using the default settings.
Moving the adTempus Database
If you are currently using SQL Server Express and want to move the database to a standalone SQL Server instance, see Moving the Database to a Standalone SQL Server. Otherwise, move or copy the database using your preferred approach.
After you have moved the database, run the Database Configuration Wizard , which will configure adTempus to point to the new database location and will configure the required database login and permissions if required.
You can also edit the database configuration directly if you prefer
Database User Mapping
When you move the database to a new database server, the database user that adTempus connects under will be present in the database, but that user may not be mapped to a server login. For example, suppose adTempus is running on computer "mydomain\server1". If you are using Windows integrated security, the database login/user with be named "mydomain\server1$". When you move the database to a new database server the database will still contain the user "mydomain\server1$" but there might not be a corresponding login at the database server level, or that login may not be correctly mapped to the database user. In that case you need to create the login (if necessary) and map it to the database.
If you use the Database Configuration Wizard this will be handled automatically if you choose the option to have adTempus create the database login for you.