PilotReports Database

Hi,

I’ve notice over the past two days our pilots report database has really grown. It’s now at about 160GB. (4*40GB).

I’m just wondering what might be causing this and if there is anything I can do to shrink the DB. There are no reports currently running. We have version 10.2.100.14

thanks.
Metesh

Metesh,
What recovery model is your database in? If it is in full mode then regular log backups should be helping maintain the growth. If you don’t have any log backups configured I’d be reviewing that there. As to why you are seeing abnormal growth. go through the following items.:

Any new reports recently configured
Any automated reports enabled (perhaps you have an autoprint setup for invoice on ship)
Any new testing occurring against that system.
Has anyone altered the Task Agent Purge Settings. System Setup>System Maintenance>System Agent
Look at your reports database and determine which are the larger tables or number of occurrences of tables that are being created. That might help you determine where the growth is coming from.

I hope that points you in the right direction.

Hi Simon,

Thank you for your help. We are using veeam backup to deal with the log backups and maintenance.

It turns out that someone had a new report configured and there was some error in their code that made it run in a loop over the weekend. That’s what made the DB grow so much. I ended up just deleting the ReportsDB and recreated it through the Admin console. The DB size went from 160GB to 54MB. :slight_smile:

thanks.

1 Like

Good solution. Sometimes I can over-complicate things :thinking:. Can you mark your post as solved. It will make it useful for future readers.

glad you found the solution… I was going to suggest another possible reason could be that someone ran multiple reports with an archive setting turned on… but that would be a lot of reports.

I suggest that you configure the reports database is “Simple Recovery” mode. Managing backups and transaction logs on this database is not very useful (in my opinion). That will help avoiding issues with the database growth.