Jeff is right about farLog - it's only functional use is to make sure bots can't brute force the webtop login, which means that it is safe to prune as much as is appropriate for your application.
Leaving refObjects records there won't break FarCry, but they can have a performance impact, so it's a good idea to clean refObjects after manually deleting records. Here's a quick-and-easy query: delete from refObjects where typename='farLog' and objectid not in (select objectid from farLog); Blair On Tue, Jan 10, 2012 at 2:18 AM, Colin Jones <[email protected]> wrote: > Our farLog table is now exceeding 2.5 million rows, which is starting > to have a noticeable effect on access in the webtop with some queries > taking 2-3 seconds to run. A few questions... > > Is it safe to "prune" farLog? > Can we just pick an arbitrary date and delete records from it before > that date? > Do we also need to delete associated refObjects entries for the farLog > data? > What are the conseuqences of doing this (simply removal of audit > data?) > > Cheers, > Colin. > > -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: [email protected] > To unsubscribe, email: [email protected] > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry > -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
