You are viewing limited content. For full access, please sign in.

Question

Question

Audit trail has reached SQL 2008 R2 limit of 10GB

Audit Trail
Updated February 12, 2014
asked on February 11, 2014

A workflow somehow had the 'User does not equal workflow) rule removed (during a very bad upgrade we think).

 

It is a little used worklow, and when we used the template after the upgrade, this created 24-40 log files a day of approximately 50MB each.  Now our audit trail database is at the SQL 2008 R2 limit of 10GB.  What is the best thing to do now?  Can I somehow delete these duplicate error logs from the database table? 

 

Our AT data is now useless as it contains all of these duplicates (it was running for about 5 days before we found the AT database was full and finally figured out why).

 

We are not using the AT database for reports yet, so we don't mind losing some (or even all) of the statistics.  We mainly got the AT as we needed it for the records management.

 

Any help or suggestions would be greatly appreciated.

0 0

Answer

SELECTED ANSWER
replied on February 11, 2014

The audit data is stored in the Laserfiche Server's binary log files. Audit Trail reads the audit data from these logs and loads them into the Audit database. You can delete your current Audit database and create a new one and then just specify the date range to avoid the day(s) when the Workflow issue occurred.

1 0

Replies

replied on February 11, 2014 • Show version history

Two points:

 

  1. You don't have to put ALL your audit data into the database. Typically, people only put the portion they need to run reports on.  For example, if you load only the last 90 days' data, the database size should be a lot more manageable.
  2. Your audit data should still be useful, since Audit Trail allows you to apply filters to the data when you're viewing reports. You can exclude all actions performed by the Workflow user, for example.

 

I hope this helps. Glad you figured out the issue!

1 0
replied on February 11, 2014

They're not duplicate and they are not error logs. They are events generated by user actions.

 

But, wording nitpicking aside, you can change the range for the data to load into the Audit Trail database to not include the date range that covers the extra activity. Audit Trail will purge events from the SQL database.

 

Although, if the database is full, it might be easier to set up Audit Trail with a clean SQL database and then add a date range that does not include those logs.

replied on February 12, 2014

Thanks very much to you both for your responses, they were very helpful.  We will get the configuration setup first and then create a new database.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...