Data mart coding standards
If you would like to report on new or changed tables in the WebSphere Commerce database then the data mart must be customized to reflect this change. The data mart can be customized at any time.
When customizing the data mart, you should follow these rules and guidelines to preserve the data mart's operational integrity:
- Do not change the definition of the primary key for WebSphere Commerce Analyzer tables.
- Do not add constraints to, or delete constraints from, WebSphere Commerce Analyzer tables.
- Do not delete any WebSphere Commerce Analyzer tables, views, columns, or rows.
- Do not alter any WebSphere Commerce Analyzer views joining, sorting, or grouping by clauses.
- Do not change the meaning of a column in a WebSphere Commerce Analyzer table:
- Do not change the data type.
- Do not change the sourcing of its data or overwrite with any sourcing.
- Do not delete any indexes in WebSphere Commerce Analyzer tables as this can affect the program efficiency.
- Do not remove any WebSphere Commerce Analyzer user-defined functions (UDF).
- Do not remove any WebSphere Commerce Analyzer stored procedures.
- Do not remove WebSphere Commerce Analyzer bufferpool or table spaces.
(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.