Cleanup of ConnectionHistory

Hello,

You are right. There is no method to clean up the ConnectionHistory table.

I will check with the developer team and get back to you.

In the meantime, the only method is doing it directly on the SQL database. If you do so, do a full database backup first.

Best regards,

Hi Andreas,

That missing cleanup feature was indeed discussed at length a looooong time ago, and at the time we felt that just allowing a purge by date was insufficient.

We saw a scenario that operators of the solution would want to prevent accidental loss of information for entries that are rarely modified. The purge would essentially delete all the history in that case. The easy fix would be an option for Keep at least X versions.

To add to the complexity. We have both (M)odifications and (D)eletions in that table, we can also RESTORE deleted entries which just restarts a cycle. This would mean that we would need to keep always the last delete, and the X modifications before?

It happens that we overthink stuff ;) But this was at the time that we were introducing PAM capabilities in our products and were focusing on preventing accidental data loss.

To be frank, RDM + SQL does just that, delete what is earlier then a date. Would you want the exact same feature or would you feel that we need that added complexity to offer you more control?

Thanks

Hi Maurice,
I can see why you discussed this and put it away on the ToDo pile ;-)

Looking at our data I can see three different approaches :

1. by date. Modification log entries older than 2 years : nobody would ever look at this again. A setting in the advanced log cleaner "connection history older than n months / years"
2. by number of entries. have a central configuration option like "keep n connection history entries" or maybe "n entries per connection per day"
3. delete / purge : have an option in the deleted entries dialog "purge history when permanently deleting an entry"

Hi,

are there any updates on possible maintenance task to ConnectionHistory table? Or at least some tested sql script that removes all modifications prior to the last one (addon: if the modifications are older that x months)? This would be very useful especially for database copy we use in a test environment (where we don't care about loosing previous versions of connections)

Best regards,
Rok

Hi,

are there any updates on possible maintenance task to ConnectionHistory table? Or at least some tested sql script that removes all modifications prior to the last one (addon: if the modifications are older that x months)? This would be very useful especially for database copy we use in a test environment (where we don't care about loosing previous versions of connections)

Best regards,
Rok

Even worse, most of entries in the connectionhistory are changes to connections modified by PAM... How do we handle that?

Hello Rok,

Thank you for your feedback.

There is no progression made on this so far. I have asked the developer team to raise the priority of our internal ticket.

We will post it here once a solution is implemented.

Thank you for being so patient.

Best regards,

Hello Rok,

I sent you the SQL statements for you to clean up the ConnectionHistory table through the ticket you opened.

If anyone is interested in obtaining the SQL statements, please contact us at service@devolutions.net referencing this forum's thread.

Best regards,