My Profile Photo

Ashley Poole

- Speaker -
- Senior Software Developer -
- Co-organiser of @ShropshireDevs -
- Site Reliability Engineering Advocate -

JAMS Database Notes

These are my notes regarding the installation of the JAMS database.

JAMS requires SQL Server and can be configured to use an existing SQL Server instance or install a SQL Express instance for you as part of the installer. If selecting an existing SQL Server instance and using Windows Authentication on your instance, then the user running the the installation must have access to create databases.

Data Files

When the database is created three data (MDF) files and file groups are created:

  1. Primary - Default.
  2. JAMS_History - Stores history information.
  3. JAMS_Volatile - Volatile and throw away information.


As part of the installation, two database roles are created called JAMSApp and JAMSReader. The first has basically has SELECT, INSERT and UPDATE where as JAMSReader only has SELECT to certain tables.

A new user is created within the JAMS database called JAMSService which by default is mapped to administrators AD group.

You may want to review these permissions and users, and adjust to your needs. This may including creating a process user for the JAMS service and granting this DBO, then deleting the other roles.

If you need to re-install the DB for JAMS follow the below instructions:

  • From the install directory of JAMS Scheudler, delete the common.settings file
  • Run JAMSDBA as an administrator
  • Type 'install' and enter
  • Follow the wizard

Posted on devops, server-admin

comments powered by Disqus