--- DENNIS WILLIAMS <[EMAIL PROTECTED]> wrote: > The key point is your users. A typical normalized > design means a lot of > tables. These tables must be joined in specific > manners. Non-I.S. users find > this intimidating. So they don't use it. So you've > spent a lot of time > creating a DW only to have nobody use it. > How many tables > did your 3nf schema > produce?
Our schema has 4 fact tables, 6 aggregates build on them and more than 20 dimension tables. And we have exctly the situation of users asking to denormalize them to simplify the report creation. > Or go ahead, build a normalized one, then > study and > build the second > version incorporating the hard-won lessons others > have learned. What I'm trying to do is to pick the best "starting point" design. Having a totally normalized schema would be one option. If the performance or report creation (in terms of simplisity) prove unsatisfactory we can change the design and denormalize to address the known issues. If however I'm able to identify the tables that can be denormalized without causing damage I'd rather do it now. __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Mother's Day is May 12th! http://shopping.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Gurelei INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
