 |
 |
Archives of the TeradataForum
Message Posted: Mon, 26 Feb 2001 @ 22:15:42 GMT
Subj: | | Re: Why not use star schema |
|
From: | | Claybourne Barrineau |
Jeff,
It is my understanding that Teradata considers Star Schemas appropriate (a necessary evil) if a 3rd normal form database design cannot
meet the response time requirements of the user.
In our case, we build Teradata Star Schema Datamarts (as part of a ROLAP application solution) weekly from a 3rd normal form Teradata
warehouse. I recommend this approach only if you are certain that a 3rd normal form solution isn't fast enough for the user, and you have
plently of disk space. Also, if you decide you do need to build a Star Schema, consider building a Multi-table Join Index to pre-resolve
your fact and dimension table joins. Our protoype of this design is running very smoothly.
Hope this helps,
Clay
| |