System Databases

Read-only database contains additional code needed for InterSystems IRIS Interoperability features, specifically the ability to create productions, which integrate separate software systems.

If you create a namespace that is interoperability-enabled, that namespace has access to the code in this database.

Read/write database used for audit records. Specifically, when you enable event logging, InterSystems IRIS writes the audit data to this database.

The IRISAUDIT database must be configured to have no maximum size. Therefore make sure to place this database where it can safely expand without impacting other critical file systems.

Read-only database that includes the object, data type, stream, and collection classes and many other class definitions. It also includes the system include files, generated INT code (for most classes), and generated OBJ code.

Read/write database that contains items used internally by InterSystems IRIS, such as cached SQL queries and CSP session information.

No customer application should directly interact with this database. This database is purely for internal use by InterSystems IRIS.

Read/write database that contains interoperability metrics.

No customer application should directly interact with this database. This database is purely for internal use by InterSystems IRIS.

The IRISMETRICS database must be configured to have no maximum size. Therefore make sure to place this database where it can safely expand without impacting other critical file systems.

Read/write database that contains security-related globals and routines. This database can be encrypted, but cannot be mirrored.

Globals in this database control system security settings and can only be accessed through the provided APIs. For details, see IRISSECURITY, the Security Database.

Read/write database includes utilities and data related to system management. It is intended to contain specific custom code and data of yours and to preserve that code and data upon upgrades.

This database contains or can contain:

• Users, roles, and other security elements (both predefined items and ones that you add).

  For reasons of security, the Management Portal handles this data differently than other data; for example, you cannot display a table of users and their passwords.

• Data for use by the NLS (National Language Support) classes: number formats, the sort order of characters, and other such details. You can load additional data.

• Your own code and data. To ensure that these items are preserved upon upgrades, use the naming conventions in Custom Items in IRISSYS.

The directory that contains this database is the system manager’s directory. The messages log (messages.log) is written to this directory, as are other log files.

For additional detail on IRISSYS, see Using Resources to Protect Assets.

Read/write database used for temporary storage. InterSystems IRIS uses this database, and you can also use it. Specifically, this database contains temporary globals. For details, see Temporary Globals and the IRISTEMP Database.

An initially empty read/write database meant for your custom code. You do not have to use this database.

Databases that provide code for IRIS for Health™ and for HealthShare®. Not available in other products.

Databases that provide access to HealthShare® features; applies only to HealthShare. Not available in other products.

Read/write database used for temporary storage used internally by InterSystems IRIS. This database is not journaled, not mirrored, and has no public permissions; it is used to store temporary globals.