Skip to content
This repository has been archived by the owner on Dec 28, 2020. It is now read-only.

Admin Manage Database

Chris Carlevato edited this page Mar 27, 2017 · 1 revision

The Database Management report contains all tables within Helios Calendar's MySQL database. This report includes the number of total rows, number of delete rows and the current table overhead (the amount of unused storage space allocated to the table - fragmented disk space).

Within Helios Calendar a deleted row is a row that contains a deleted item (event, location, etc.) which is present within the database but has been flagged not to be used within the application.

Purge Deleted Rows

For some data items Helios Calendar does not permanently remove the record(s) from the database when the data is deleted. This data is still available within the database, however, it is “deleted” from the application. This is done so that the deleted data can be restored manually if needed. The Database Management tool allows permanent purging all deleted data from the Helios Calendar database.

To permanently purge deleted data click the “Purge Deleted Rows” button. Purging deleted data will result in increased table overhead (fragmentation).

Note: Use caution when purging the database. Purging will permanently delete the data from the database. This process cannot be reversed unless the database is restored from a backup that contains the deleted data.

Optimize Tables

MySQL tables, over time, can become fragmented - like any storage medium - leading to decreased performance. By using the OPTIMIZE command MySQL will rebuild tables, filling fragmented space and reducing the tables' disk usage. It is recommended to optimize the database after purging as deleting large groups of table rows can increase fragmentation.

To optimize your Helios Calendar database click the “Optimize Tables” button.

Clone this wiki locally