Re: Denormalize when developing apps (for aggregate display puposes)?
Date: Fri, 21 Nov 2003 14:03:31 -0500
Message-ID: <H4ednZNcErdC_COiRVn-gw_at_golden.net>
"OlegJay" <olegjay_at_yahoo.com> wrote in message
news:47d21956.0311210912.90d6f8_at_posting.google.com...
> I know that denormalization is fine for the purpose of speeding up
> queries but is it appropriate to denormalize for an app like Forms?
>
> We're currently between the design/build stage of a medium sized OLTP
> database. The logical & physical designs are currently beautifully
> normalized.
Why would anyone normalize a physical design?
> There will be one main Form & several Reports built for this database.
> The Oracle Form builders say that I must denormalize (by adding two
> redundant columns from one table to two other tables) the physical
> model in order for their Form to display all the user requirements.
> (The user wants the Form to look and aggregate data exactly like their
> legacy Paper printout form.)
The first question is: Is it the tool or the builders who are incompetent? Received on Fri Nov 21 2003 - 20:03:31 CET