Because reports that rely on the Pages table are especially likely to have many unique items, table limiting is a special concern for these reports. If your Pages reports become very large, you may need to change your configuration to use these reports more effectively.
The following reports rely on the Pages table:
- Single Level Paths - Forward
- Single Level Paths - Reverse
- Single Level Paths - Forward and Reverse
- Paths - Forward and Reverse Reports
- Top Entry Pages
- Top Exit Pages
- Any custom report based on a dimension using Pages
Monitor table activity for these reports as described in the
following troubleshooting instructions. Keep in mind that if you use Webtrends
Analytics 9, you cannot
adjust table limits. Contact your account representative if you believe you are
experiencing a problem that requires changing table limits.
- To determine whether your Pages reports are reaching their limits, or if you
suspect unique URLs are not being collected and added to your reports, use
Profile Monitoring to check your table activity.
- If the Pages table is nearing or has reached its limit, consider raising the
- If your Pages table is very large, you may find that raising the table limit
slows performance to an unacceptable level or causes Webtrends
Analytics 9 to fail.
If this occurs, make sure your installation is configured for best performance
and minimal resource consumption. For example:
- Make sure your profile does not include a large number of reports, especially other resource-intensive reports. Disable any reports you do not need. If necessary, you can create a separate profile for Pages reports.
- Make sure you have enough physical and virtual memory to support your installation. See the Release Notes for sizing considerations.
- Try disabling resource-intensive features such as Visitor History collection and interval data, which are not required for Pages reports.
- Disable page title lookups in your profile. If you tag your
pages using Webtrends query
parameters for Webtrends Analytics 9 or
SmartSource Data Collector, be sure you use the WT.ti query parameter to identify page titles.
- Try using the URL Rebuilding feature to reduce the number of unique pages. URL
Rebuilding allows you to decide which URL parameters should be included in page
URLs that are collected in the Pages table. For example, if every URL contains a
unique session ID, hits to the same page are counted as different pages and
inflate the number of pages in the Pages table.
Keep in mind that you can still report on a URL parameter even if you exclude it from the Pages reports using URL Rebuilding. For example, if you remove a parameter that indicates the product ID from the Pages report, you can still report on the parameter using URL Parameter Analysis, and you can still use the standard Products reports with a translation file. If you are licensed to create custom reports, you can also build a custom report that shows a complete list of product IDs.
- If you have problems with too many unique URLs that are not caused by URL
parameters, you may want to try using URL Search and Replace to remove unique