Optimizing profiles for reports with large numbers of rows with report periods


Webtrends Analytics 8.x
Webtrends Analytics 9.x


Some reports contain a large quantity of unique items that can exceed table limits over time.For example, search phrase-based reports contain many different terms; there are multiple terms used to search for the same thing and these include misspellings.When a table is full new terms may not show in the report even if ithas more hits than existing terms.


A standard profile uses a yearly table that saves all unique dimension elements.The table collects new unique dimension entries (rows) through the calendar year, resetting the table at the end of the year.Some dimensions have so many unique row entries that the table size cannot be made large enough to last a year without affecting analysis performance.

Wheremore unique itemsare needed the profile can be configured to reset the table monthly rather than yearly.

1. Edit the profile.

2. Go to Reports > Report Periods.

3. Select only the Monthly and Daily report types.

4. Save the profile.

What you gain:

  • Tables reset at the end of every month allowing more unique elements over time.Each month is only the elements for that month not cumulative for the year.
  • Monthly and daily reports are normal.

What you lose:

  • You can’t select a week in the user interface and a custom range data of a week is not de-duplicated.
  • No quarterly or yearly rollup reports.
  • Data at the start of every month is from a new table (not just January).

Best practice is to create special monthly profiles for the reports requiring monthly table resets.Use profiles with all report periods enabled for your regular reports.

For extreme cases of numbers of unique elementsselect only the Daily reportperiod.The tablewill reset every day instead of every month.

More Information

Note: If the above-mentioned changes are made to an existing profile with the quarterly and/or yearly period enabled, even though the monthly period is now the largest reporting the larger reporting periods remain open until the period ends and they are able to close. The reason for this is because reporting periods must close gracefully and the smaller reporting periods have dependencies in the larger framework. It is advised to select specific reporting periods on newly created profiles rather than make these changes to existing profiles as it will result in losing the progress to date for the larger period and keep the tables open, thereby affecting table limits for the target periods for the remainder of the largest period.