i am not quite sure if your problem is a backlog of events that have not
been processed due to the disabled generator or loads of history data for
events that have been processed and have not been vacuumed out.
for the former,
the incoming events are collected into the ns<app>eventbatches table in the
instance database to wait for te generator to start. you could purge this
table to remove the backlog of events. you could also adjust the quantum
clock forward using setquantumclockdate to help it catch up and ignore all
those old unprocessed quantums.
if it is the latter and you just have history data for events that have been
processed and there is so much that the vacuumer is going to run forever then
i would just suggest an overnight job wich runs the vacuumer for short
quantum intervals to remove the history bit by bit.
hope this helps
"Dave Saylor" wrote:
> I was asked to look into a problem a customer was having , Turned out they
> moved SMTP server and in the process the generator got disabled. This was
> back in May.
> So I have that all squared away and now I'm looking for a quick way to clear
> out the events that have been backing up.
> Vacuum was never scheduled and as a result there are over a million Quantums
> left to be cleaned. Running manual results in 2500 an hour.
> Does anybody know a way I can just clean out the existing events with out
> delete / create? Or just what the options are..
> Thanks in advance