OctopusDeploy Database size

[David_Gutzmann]

Hi

we just hit the 10GB database size limit of the Express Edition and in turn had to upgrade the SQL Server Edition.

We seem to have quite a lot of rows in the dbo.Event and dbo.EventRelatedDocument tables:

Are those two tables covered by retention policies? What would be a safe way to go about getting rid of say anything older than a couple of months on a regular schedule?

Kind regards

David

[donny.bell]

Hi David,

Thank you for reaching out.

You are correct, implementing a retention policy will reduce the size of the dbo.Event and dbo.EventRelatedDocument tables. However, it probably won’t be too drastic.

We don’t normally recommend manually deletion due to the impact it will have on your audit log.

Hopefully this clears things up. If you have any more questions, don’t hesitate to ask.

Regards,
Donny

[David_Gutzmann]

Hi Donny

Thank you for your swift reply.

We do have retention policies in place, however, we also use Runbooks to trigger stuff. Those Runbooks run every couple of seconds and from what I see in the Audit log, every run creates several new entries in the log.

We would be very OK with not having history for Runbook runs from months back. Could you provide us with some insight into what would be “safe” to delete from those tables?

Thanks again,

David

[donny.bell]

Hi David,

Thanks for getting back to me.

Runbooks keeps a finite number of runs (I believe 100?). I’m not sure there would be much to gain there.

As I touched on previously, we generally do not recommend manually deleting anything in the db unless there is some sort of major performance issue preventing Octopus from working properly. We are currently exploring adding additional features to Octopus that would give our customers more control over data retention.

I’m sorry. I wish I had a better answer for you. If you have any more questions don’t hesitate to ask.

Regards,
Donny