In the JetServices database, the ReportRuns table has become very large. That table keeps the run history of reports that are published to the Jet Hub. Given the size of the table, it also appears to keep the report itself in a BLOB.
Is it safe to delete old records in this table? Is there a function within Jet to clear this table, or not keep them in the first place? The data is very dynamic, so the old reports are pretty much useless.
Hi, I have the same issue here. Did you get any answer ?
There should be no issue in deleting older records from the dbo.ReportRun table.
If I wanted to delete anything older than 6 months, I could use a query such as this:
DELETE from dbo.ReportRuns WHERE Runtime < '2018-07-01'
Thanks, wasn't sure if that was the most prudent.
We can make that more dynamic with the following, which will delete all records older than 30 days:
DELETE FROM [dbo].[ReportRuns] WHERE (DATEDIFF(DD, [Runtime], GETDATE()) > 30)
The other thing I found out was the reason for this problem. This table was growing quickly. As it turns out, a user had mistakenly set up a scheduled job that was set to run every few minutes. Additionally, the SMTP settings were not configured, so I guess when Jet can't send it out, it keeps it in this table as an archive. That adds up quite quickly.
To find out which user was causing this, I had to look through the ScheduledTask tables and see which user had a task. Then had to log in to that users portal and disable the report.
Thank you T-Man... Our issue was the same... A user setup a scheduled report 6 times... running every minute... It is all solved now. Thank you all for your answers.