Periodically, you should review the Database Table Size report, which contains details on the daily and monthly growth patterns of dimension data.

Note: Immediately after installation or configuring a Whitelist + Observed Values, review this report on a daily basis. Over time, you may lengthen the period between review.

1. From the Portal menu, navigate to System Status > Database Table Size.
2. From the drop-down, select Dimension.
3. Set Focus Period to an appropriate date range.
4. Download report.
5. Load into Excel.
6. Sort by the Daily growth, Monthly growth, or row count column to identify the fastest-growing or largest dimensions.
7. Based on the values for specific dimension tables, you can determine whether configuration changes must be made to the dimension.

   The tables of interest are listed as TD_DIMENSION_XXX, where XXX is a numeric identifier.

   Note: The _LOG table references indicate dimensions that have logging enabled to capture detected values.

Purge dimension data

You can purge the data for individual dimensions through the Event Manager.

When a dimension is purged, it is automatically switched to Whitelist Only method of recording.

• If you specified a whitelist, it is retained.
• If you not specified a whitelist, no data is captured to the dimension until you enable logging, download values, and then upload your defined whitelist.
• Dimension blacklists and group lists are not retained.

Note: Purging dimension data removes all dimension values stored in the database for the selected dimension. This purging can impact multiple reports and other data objects in the Tealeaf system. Review the warnings before purging dimension data.

Changes to the application

When your web application development team changes your web application, you may need to change your dimension whitelists.

For example, if you defined a whitelist to manage URLs, changes to the URLs for the web application may not appear in the whitelist and balloons the counts for the [Others] category.

Note: If possible, ask your web application team to keep you apprised of changes to the web application. For example, if they can produce a definitive set of URLs for each revision of the web application, you can quickly update the whitelists for URL-related dimensions.

Additionally, hit attributes are likely to be impacted by changes to the web application.