We're are experiencing performance problems with the course stats & the
activity accumulator because of the rate our activity accumulator table
is growing: 40 million rows from the last six months. Over 75% of the
growth relates to logging of displaying 'tabs' and 'modules' in the
community system, which we are not interested in.
Has anyone selectively deleted logging from BB_BB60.ACTIVITY_ACCUMULATOR
or BB_BB60_STATS.ACTIVITY_ACCUMULATOR based upon EVENT_TYPE? If so, did
you encounter any problems as a result? Do you mind sharing the SQL
command you used? Was this action supported by your TSM?
Is course statistics reporting done from BB_BB60.ACTIVITY_ACCUMULATOR,
BB_BB60_STATS.ACTIVITY_ACCUMULATOR or both?
To compound the problem we effectively have two copies (of the 40
million rows) in both: BB_BB60_STATS.ACTIVITY_ACCUMULATOR and
BB_BB60.ACTIVITY_ACCUMULATOR. The later contains everything the former
one does, plus a few extra days beyond the 180 days logged in BB_BB60
and minus the most recent day.
Is there a way to have days 0 - 180 in BB_BB60 , and days - 181 -
onward, in BB_BB60_STATS?
Otherwise is it possible to have days 0 - 180 in BB_BB60 and nothing in
BB_BB60_STATS?
Sorry about the huge list of questions. Any help / guidance / info would
be very gratefully received.
Thanks,
Paul
|