Basically Martijn is correct. If you have problems with speed related
to reporting, then
create a data mart / data warehouse. That is what they are for. Don't
sacrifice your
DB design for speed. Make it logical and accurate first.

Martijn Tonies wrote:

>Hi,
>
>
>
>>>What "fastest" - table design shouldn't be about speed, but about
>>>consistency and normalized data structures.
>>>
>>>
>>I must desagree with you! I think database design has a *lot* to do with
>>speed (performance).
>>
>>
>
>Not at all. Design is a logical process while performance is a physical one.
>
>Instead of designing for performance, db engine vendors should either
>code their engine better or you should throw in some hardware.
>
>Designing for performance creates - most of the time - only more problems.
>
>With regards,
>
>Martijn Tonies
>InterBase Workbench - the developer tool for InterBase & Firebird
>Firebird Workbench - the developer tool for Firebird
>Upscene Productions
>http://www.upscene.com
>
>"This is an object-oriented system.
>If we change anything, the users object."
>
>
>
>To unsubscribe from this group, send an email to:
>ib-support-unsubscribe@egroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
>

--
Thomas Miller
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork

http://www.bss-software.com
http://sourceforge.net/projects/dbexpressplus