Certain tables in the ResourceXpress database are updated with new records on a regular basis. Some of these tables store vital application information, such as Bookings records, while others record device and 3rd party booking system activity which can be useful when troubleshooting a problem.
Having too many records in the database can lead to application performance issues, it can also lead to a large quota of storage being consumed by the database. Scheduled maintenance on the Resourcexpress database is therefore strongly recommended to ensure performance is not affected and storage limits are not reached.
Plan and Decide
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 lists the database tables that can be maintained with descriptions of the records held in those tables.
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. |
*Records are not generated when the profile is in Energy Saving Mode
Available Maintenance Actions
There are four available actions for each of the above tables
Delete
The delete action will remove all records from the live target table. Records will not be archived and cannot be retrieved.
Deleting will improve performance and reduces the size of the database.
Archive
The archive option will move the records from the live table to an archive table. Records in an archive table cannot be viewed from the application UI but can be queried directly from the database.
When archiving, you specify the number of days worth of records to retain in the archive table.
Archiving will improve performance as the records do not interfere with application lookups however they still take up the same amount of storage space.
Take No Action
No records will be deleted or archived from the live table.
No performance or storage benefits apply to this option.