Originally Posted by
DrByte
Well, technically the admin activity log shouldn't have much of an impact, as there is no attempt to retrieve records from it ... only to insert user-tracking data for audit-trail purposes. While inserts can be slow if there are a lot of indexes on a given table, this is a very simple table, and inserts should be very fast.
However, given that flushing the table has concurrently met with improved speed, it's difficult to rule one way or the other.
Certainly, size was one reason for the alert being added. This is the first I've noticed that this table might be related to a performance problem.
John said that he "cleared out" the log. This suggests a truncate, rather than a drop and recreate, so it doesn't sound as though the table structure or index settings were the culprit, but rather, if this table was the cause, then it would have to be sheer size leading to the symptoms.
"Hmmmmmm......."
Bookmarks