From: Martijn Tonies
Date: August 29 2008 8:42am
Subject: Re: Normalization vs. Performance
List-Archive: http://lists.mysql.com/mysql/214291
Message-Id: <00ea01c909b3$3c912170$9902a8c0@martijnws>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> > So how bad is this? The mentioned query will be the query which is used
> > the most in my application (yes, it is going to be a forum).
> > Should I break normalization and save the date of the root in each node
row?
>
> My recommendation is no.  Normalization is a Good Thing, and you'll be
> hard-pressed to convince me otherwise.  In the long run, you (or
> following programmers) will thank yourself if you maintain a normalized
> core data model.  Seriously.
>
> But speed and performance are the here-and-now issues while DB
> technology "catches up" to demands.  Have you looked at temporary tables
> or materialized views?  These might help you in this endeavor.
>
> Kevin

I'm with Kevin on this one.

Normalize.

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com