Reading out the Application configuration of Litmus Production Record Database

use cases litmus production record database keeps required settings in an internal table, which can be read by users user can do this either by using applications such as microsoft sql server management studio mssql cli this can also be used for building custom solutions based on applications which allow for an odbc connection such as excel c# net python method run s elect query with view prorec misc getappconfig as from clause how to use to read out the application configuration of litmus production record database, execute a select statement from the view prorec misc getappconfig below is an example using t sql in sql server management studio result the view returns a table as result example for a windows installation example for a linux installation understanding the output configuration items which can be changed configitem description changeable? days to keep log the number of days for which to keep data in the log tables before purging the tables impacted are prorec event log prorec misc log prorec tag log prorec prorec log prorec error log yes days to keep prorec the number of days for which to keep production record event data before writing them into a backup text file and purging them yes days to keep tag the number of days for which to keep tag data before writing them into a backup text file and purging them yes misc transaction count 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 misc transac maxage 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 backup path 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 backup file seed tag this is the prefix used for naming the backup files for tag data yes backup file seed tag meta this is the prefix used for naming the backup files for tag data meta data yes backup file seed this is the prefix used for naming the backup files for production record event data yes queue monitor graze period 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 scheduler nextrunahead this is the time in minutes into the future at which a newly scheduled task can execute the earliest yes misc transaction count mode 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 max waittime broker sid this time in seconds is used by the system to identify blocking sid's to be able to clear them yes hierarchy backup file seed this is the prefix used for naming the backup files for production record data model hierarchies yes tag hierarchy backup file seed this is the prefix used for naming the backup files for tag definitions yes at servicebroker verbose 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 hours to keep at log the number of hours for which to keep data in the log table before purging the tables impacted are prorec at servicebroker logs yes debug log this is a flag which can be used to control the type of log entries made into the table prorec event log prorec misc log prorec tag log prorec prorec log 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 maxidentifiers 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 yes configuration items which can not be changed configitem description changeable? failed trans count \<x> this is an internal value which is created for every data model where \<x> is the data models id the value represents the number of items and is used to facilitate how often to try to reprocess production record events if they failed to process for example because of missing identifiers no