...
Some planning and decision-making will be required before configuring and executing the database maintenance tasks described below. Consideration should be made on how you consume and report on data in ResourceXpress and how troubleshooting could be affected when records are deleted.
Target Tables
The following Table 1.0 lists the database tables that can be maintained with descriptions of the records held in those tables.
Table 1.0
Table Name | Description | Potential Growth |
|---|---|---|
dbo.ConnectivityLog | ||
dbo.BookingSystemConnectivityLog | ||
dbo.QubiActivityLog | Connections to the application from a Qubi 2, Qubi 3 or TD-0350 desk device are stored here. | Each of the listed desk devices will create 1 record every 60 seconds. To calculate the amount of records generated in a 24 hour period you can multiply the number of desk devices in your environment by 1440 e.g. 60 Qubis would be 60 * 1440 = 86,400 records in a 24 hour period.* |
dbo.Bookings | Local bookings and 3rd party booking system records. | Each booking either created locally in the application or syncronised from a 3rd party booking system will create 1 record per configured profile. |
dbo.ResourceMessages | Admin configured resource messages that are broadcast to Room Screens and Kiosks | Resource Messages records still persist in the database even after the configured expiry date has passed. If the message is deleted from the admin console it is also removed from the database. |
dbo.EquipmentProblems | Any “Call for Help” reports for faulty equipment or other resources made from Room Screens or Kiosks. | Equipment Problem records persist in the database even when the problem has been closed in the admin console. |
...
No performance or storage benefits apply to this option.
Configuring Maintenence Actions
Configuring the available maintenance actions is carried out in the ResourceXpress database and involves executing SQL queries to set your desired configuration.
Table 1.1 describes the available actions and their respective SQL values.
Table 1.2 shows the relevant SQL column names and the value configured by default.
Table 1.1
Action Description | SQL Value |
|---|---|
Delete | 0 |
Archive | Any positive number i.e. 1, 2, 3 etc. The number configured will be the number of days records will be archived |
Take No Action | NULL |
Table 1.2
Column Name | Default Value |
|---|---|
ConnectivityLogDaysToKeep | 0 = Delete all records |
BookingSystemConnectivityLogDaysToKeep | 0 = Delete all records |
QubiActivityLogDaysToKeep | 1 = Archive for 1 day |
BookingDaysToKeep | NULL = Take no action |
ResourceMessagesDaysToKeep | NULL = Take no action |
EquipmentProblemsDaysToKeep | NULL = Take no action |
ConnectivityLogArchiveDaysToKeep | 0 = Delete all records |
BookingSystemConnectivityLogArchiveDaysToKeep | 0 = Delete all records |
QubiActivityLogArchiveDaysToKeep | 1 = Archive for 1 day |
BookingArchiveDaysToKeep | NULL = Take no action |
ResourceMessagesArchiveDaysToKeep | NULL = Take no action |
EquipmentProblemsArchiveDaysToKeep | NULL = Take no action |