| |
| |
Teradata Magazine | Project needs and the enterprise view - using EDW design layers to bridge the divide |
 | | Database views should, however, be the first consideration in addressing reporting, application, and analysis requirements as they provide the highest level of consistency. |
 | | If database views do not meet performance needs, the next consideration should be materialized views, as these are always maintained to be up to date with changes to the tables they are based upon. |
 | | Database views, materialized views, and propagated tables can be set up for snapshots of the current view, actual historical profiles, forecasted views, current and future-oriented reference data with transactional data recast, and lifecycle structures reflecting changes over time. |
| www.teradata.com /t/page/145854/index.html (3577 words) |
|