Comments on: You need to read this post about Table Limits

By: rocky

rocky — Wed, 10 Feb 2010 21:39:45 +0000

Good point. There is about 50 times more info coming out of WebTrends about the dangers of high limits than there is about the dangers of low limits. We’ll definitely incorporate the high limit info they provide.

Sean – At the WebTrends Engage conference last week, we learned that table limits are a much bigger deal than we’d thought. Apparently WebTrends gets bad feedback on it from big important customers as well as us tiny (still important) customers. And, in software 8.7, WebTrends has addressed it. First, the code in 8.7 allows much bigger table limits without as much impact on performance. Second, they have added table limits as an Alert topic — you can set up warnings to yourself about nearing table fill-ups.

We’re still going to finish the series since so many of us aren’t planning on going to 8.7 any time soon.

By: Rick

Rick — Wed, 10 Feb 2010 15:56:15 +0000

Great post. You mentioned that this is likely 1 of 3 or 4 posts on this topic. I’d like to suggest that you incorporate the performance impacts of increasing table sizes. Webtrends technical support has warned me about this in the past, but then is vague about the specific impacts.

By: Sean

Sean — Fri, 05 Feb 2010 12:24:58 +0000

Your presentations at WT Engage were amazing! Also, I’ve heard the table limits question is quite a big one internally there. Did you learn anything about progress?

By: rocky

rocky — Thu, 04 Feb 2010 13:44:44 +0000

Good point, Mitchell, it’s now on the list … unless YOU want to flesh that out?

By: MitchellT

MitchellT — Thu, 04 Feb 2010 10:38:05 +0000

Thanks for this monumental post. Sooner or later all who work with Webtrends software will encounter this issue either on our own installations or another we may be called to review. I could not agree more about the need to monitor table sizes and the need to have it documented in a clear, obvious way so that the topic is approachable ad meaningful to WT admins.

The good news is that because we’re using logs, and because we’re using the software version, we can always reanalyze and get the info back into our reports. But this can take a lot of time and elbow grease.

Again, thanks for this post – we need to float this one into the top 10 list, call to make this topic a part of training, and expose it to new users at every opportunity.

Another good post would be how to break up profiles in a meaningful way to better manage table limits and custom report limits.