 |
 |
Hi Paul, The idea is that you keep your Bb_Bb60 activity table small - keeping only a few months of data - whilst having everything continually being fed into your stats database. You can set the purge tool to purge all data older than a certain date from your Bb_Bb60 activity table. This keeps the performance of your production database up where you want it. You just need to set the DAYS TO KEEP value to, say 180 days and everything older gets removed. The purge tool runs nightly on our installation. When you run queries to get usage data you should run them against your stats database as this will hold everything. Hope that helps? ...................................................... Gerard Elder VLE Systems Development Officer Blackboard Administrator City of Sunderland College [log in to unmask] tel: 0191 5116005 fax: 0191 5116163 ...................................................... -----Original Message----- From: Blackboard/Courseinfo userslist [mailto:[log in to unmask]] On Behalf Of Beckett Paul Mr (ITCS) Sent: 14 February 2008 17:48 To: [log in to unmask] Subject: ACTIVITY_ACCUMULTOR table : excessive logging 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