Can i truncate housekeeper table?

[Chanakyar11]

Hi,

We somehow missed to enable housekeeeing on history and trends tables for couple of weeks and re-enabled right when we realized data is growing significantly. However, delete statement on housekeeper table is hours and eventually slowing down things. Also, inserts into housekeeper are "waiting table flush" locking the whole database.

To get over this problem, is it a good idea to truncate 'housekeeper' table and stick to partitions for history and trends tables ?

Thanks in advance!!

[Chanakyar11]

Can i truncate housekeeper table?

Can i expect any application interruptions after truncating the table ?
Please help.

[bvlad]

I actually just did this. No issues noticed so far and no interruption of service.

[Chanakyar11]

Thanks for the response bvlad !!
Even i truncated housekeeper and not experiencing any interruptions.
However, restored the backup that was taken before truncating the table as housekeeper_new and created a insert after trigger on the table to apply all the inserts from the housekeper table.
(If in case the application experiences any interruptions, we can quickly rename the new table as housekeeper and drop the existing one)