Reading out the Application configuration of Litmus Production Record Database

The number of days for which to keep data in the log tables before purging. The tables impacted are:

Yes

The number of days for which to keep production record event data before writing them into a backup text file and purging them.

Yes

The number of days for which to keep tag data before writing them into a backup text file and purging them.

Yes

To prevent that a large number single data point insert can cause a performance slow down, the application will automatically monitor the average number of data points written to the database in a 5 second interval every 5 minutes. This number of data points is then used, to create a batch of this size of data before processing them. The largest batch can be 500. Users can modify this value, for example if they change to a note periodic data insert method.

But the value can be overwritten by the automated routine if it detects a change which could cause a slower performance and the value for the config item "Misc_Transaction_Count_Mode" is set to 1.

Yes

To ensure, data are not stuck in the transaction tables and are always processed, the system checks frequently for old data. To define what is considered old data, the system does use this value which is the age in minutes to verify if they should be processed.

Yes

This is the path where the backup files will be stored. By default, the system will use the same path used by the database.

Yes

This is the prefix used for naming the backup files for tag data.

Yes

This is the prefix used for naming the backup files for tag data meta data.

Yes

This is the prefix used for naming the backup files for production record event data.

Yes

The system constantly does monitor if any procedures which are scheduled have executed. In the case of a system restart, this value in minutes is used to give the system enough time to get up and running before monitoring again.

Yes

This is the time in minutes into the future at which a newly scheduled task can execute the earliest

Yes

This allows the user to enable or disable the automated monitoring for the transactions tables. If disabled, the system will use the value provided by the config item "Misc_Transaction_Count" and does not adjust it.

Yes

This time in seconds is used by the system to identify blocking SID's to be able to clear them.

Yes

This is the prefix used for naming the backup files for production record data model hierarchies.

Yes

This is the prefix used for naming the backup files for tag definitions.

Yes

This is a flag which can be used to control the type of log entries made into the table PROREC_AT_ServiceBroker_Logs.

By default the value is 0 which disables the logging of any asynchronous query execution to save on disc pace used for the log table. The value 1 will enable logging.

Yes

The number of hours for which to keep data in the log table before purging. The tables impacted are:

Yes

This is a flag which can be used to control the type of log entries made into the table:

By default the value is 0 which will only store the start and end of an activity with no further detail. The value 1 will enable detailed logging. This will increase the number of rows stored in the log tables and therefore will also require more disc space.

Yes

This value is used by the event monitoring subsystem. To be able to allocate new events correctly an assistance table calld PROREC_Event_Events_Identifiers is used to record when the Event monitoring subsystem found new identifier combinations including their exact timestamp. This is done before the data are actually stored in the Production Record data storage.

To not have this assistance table hold to much unnecessary data, it is regularly (every 15 minutes) trimmed to this number of records for each event.