Data storage requirements

Use this information to help determine the hard disk requirements for the WebSphere Commerce Analyzer server.

The storage requirement formulas are included, grouped by schema. Refer to Table sizes and tables space names for the sum of the column size required in the formulas.

WebSphere Commerce Analyzer schema

The WebSphere Commerce Analyzer schema holds the WebSphere Commerce Analyzer data mart. Use the following formula for tables in the WebSphere Commerce Analyzer schema:

Table size = (sum of the column sizes in bytes) * (number of rows inserted)

WCATMP schema

WCATMP schema tables are used to find the last valid update during the run cycle for unique record occurrence based on the primary key of the table. These tables are cleared between runs and are not affected by initial replication and extraction.

Use the following formula for tables in the WCATMP schema:

Table size = (sum of the column sizes in bytes) * (number of update records processed)

WCAETL schema

WCAETL schema tables are used to transform the data before it populates the WebSphere Commerce Analyzer data mart tables. Use the following formulas to determine the space required for these tables:

WCAETL schema Table Formula
BROWSER1_INFO

This table never has more than 1000 rows.

DMT_MEMBER_T

Table size = (sum of the column sizes in bytes) * (number of records in the WebSphere Commerce Analyzer MEMBER table)

FE_CLICKS_T

Table size = (sum of the column sizes in bytes) * (maximum incremental number of clickinfo pathinfo type records in the USRTRAFFIC_R table)

Note: (pathinfo is a field in the USRTRAFFIC_R table)

FE_REFURL_T

Table size = (sum of the column sizes in bytes) * (maximum incremental number of USRTRAFFIC_R records)

FE_FOI_T

Table size = (sum of the column sizes in bytes) * (maximum incremental number of ORDERITEMS_R records)

FE_UPDS_T

Table size = (sum of the column sizes in bytes) * (maximum incremental number of ORDERITEMS_R records)

FM_FOI_T

Table size = (sum of the column sizes in bytes) * (maximum incremental number of pathinfo records ending in *jsp in the USRTRAFFIC_R table)

FM_UPDATE_T

Table size = (sum of the column sizes in bytes) * (maximum incremental number of pathinfo records ending in *jsp in the USRTRAFFIC_R table)

FM_UPDS_T

Table size = (sum of the column sizes in bytes) * (maximum incremental number of pathinfo records ending in *jsp in the USRTRAFFIC_R table)

FO_OITEM_T

Table size = (sum of the column sizes in bytes) * (maximum incremental number of ORDERITEMS_R records)

ORDER_CURRENCY_REF

Table size = (sum of the column sizes in bytes) * (maximum incremental number of ORDERS_R records)

ORD_CREATE_DATE

Table size = (sum of the column sizes in bytes) * (maximum incremental number of ORDERITEMS_R records)

RPT_MEMBER_T

Table size = (sum of the column sizes in bytes) * (maximum number of non-repeat_customer records in the WebSphere Commerce Analyzer .member table)

TEM_CURRENCY_CON

This table never has more than 1000 rows.

T_ORDERS_PER_HOUR

Table size = (sum of the column sizes in bytes) * (maximum incremental number of ORDERS_R records)

IWH and IWHWSA schemas

For tables using the IWH and IWHWSA schemas, use the following formula: Table size = (sum of column sizes in bytes) * (average daily volumes)

These sizings must allow enough space for the initial replication and extraction. You can calculate the ongoing space requirements using these formulas. The sizing must allow for initial load. Space can be recovered using the results of the previously-defined formulas.

Note: The previous formula assumes that you conduct incremental processing daily. However, this processing might take place several times per day, weekly, or monthly.

For more information on these schemas, see the DB2 Data Warehouse Center documentation.

Feedback