Removing the 11,000+ Entries in History

just dropped sonarr.db into it and got a nice list.

I make a point of this the second I notice something has been grabbed and I have verified it.

If I do anything I will make a copy of the untouched sonarr.db file on my desktop.

It did mess something up. I added a new series to find a missing episode from OTA tv and its not populating. When I try to refresh to get the series list it is failing. I see in the logs the ā€œdatabase disk image is malformedā€ So back to the drawing board. I will put the old .db back. Bummer.

Putting it back fixed it and I added the series and everything populated… and the missing shows are downloading.

And my history is up to 11427 records. .

I currently have 5,211 going back to at least 2021. It’s truly outragous.

Confident, but wrong. It absolutely is used for tracking what has been imported, whether you want to believe that or understand why it might be necessary

In the 2 hours question was answered and you responded? Maybe you should demand an answer on Reddit again?

And yes I’m aware there were posts before that, but I didn’t have anything to respond with at the time, but you seem to have enough responses for everyone.

You’re on the right track, open it up in your SQLite tool of choice and drop all the items in the history. DELETE FROM History, some recently imported things might pop up in the queue again though and it’s not something we specifically support.

At this time we do not have plans to add a setting, option, button or otherwise to trim history, but if you want to do it (and understand that it’s not supported by us) you can clear out the History table from the database directly. Maybe that’ll change in the future, but for the time being we already have a pile of things we’ve already committed to working on.

Thanks Marcus, This time I won’t delete the downloadedfiles table and see if that works better.

Yeah, don’t delete a table, that will definitely brick things.

Let’s not pretend that I’m the one in the wrong when we both know better.

Dude, we got a fix. Let sleeping dogs lie…

Oh, not the table. the downloadhistory rows… oops. Can I do the same for that one too and not screw things up?

No need to fix this, I can document what I did and post it as the solution.

1 Like

Yeah, that one should be about as safe to do as well.