Patrick,
Then you're still dealing with normalized data for your main database. Just
your reporting database is flat...
Gerry
On 3/8/06, Patrick Newberry <[EMAIL PROTECTED]> wrote:
>
> When you say efficiency, it depends on efficiency for what.
>
> There is efficiency for storage... That is where normalization comes in,
> But for some situation like some reporting requirements, de-normalized
> reporting tables can prove to be much faster because you can reduce the
> number of joins. Thus it runs more efficiently but is not as storage
> efficient.
>
> These reporting tables are not updated directly but are build from the
> normalized tables which are accessed and used by the update pages
> associated with them. We only build them twice a day so the reports are
> not real time but if you saw how much data is being packed into these
> reports and how large the tables are, you'd understand.
>
[Non-text portions of this message have been removed]
The php_mysql group is dedicated to learn more about the PHP/MySQL web database
possibilities through group learning.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/php_mysql/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
