rsday, September 22, 2005 2:17 PM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Subject: Re: good database design
Tim Hayes wrote:
I disagree completely.
I prefer to have regard to the statement of requirement, which in this
case is a concern over performance. If following conventional design
t: Re: good database design
> This is an interesting subject area.
>
> In a data warehousing environment, one tends to adopt table structures
such
> as snowflake layouts which lead to improved performance.
>
> Createing a perfect normalised database design may well lead to
perform
> This is an interesting subject area.
>
> In a data warehousing environment, one tends to adopt table structures
such
> as snowflake layouts which lead to improved performance.
>
> Createing a perfect normalised database design may well lead to
performance
> issues.
If this is the case, go bug
Hi,
> > Given that the OP did not state that there were any issues with an
> > existing website, logical requirements come first. Period. No discussion
;)
>
> Logical requirements may come first, but may be overruled later by
> requirements caused by performance issues or system limitations.
Whic
Martijn Tonies wrote:
Given that the OP did not state that there were any issues with an
existing website, logical requirements come first. Period. No discussion ;)
Logical requirements may come first, but may be overruled later by
requirements caused by performance issues or system limitation
that when it
comes to online performance, sometimes you have to break the rules.
-Original Message-
From: Sujay Koduri [mailto:[EMAIL PROTECTED]
Sent: 22 September 2005 09:58
To: Ian Sales (DBA); [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Subject: RE: good database design
My 2 cents
d now actually you should start worrying abt the DB Tuning and harware
requirements.
sujay
-Original Message-
From: Ian Sales (DBA) [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 22, 2005 2:17 PM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com
Subject: Re: good database design
Tim
Tim Hayes wrote:
I disagree completely.
I prefer to have regard to the statement of requirement, which in this case
is a concern over performance. If following conventional design rules
creates performance issues, then performance related issues come first when
considering design.
- persona
, any link, any info, any word is important
forme. I can't find the right start point.
Thanks
OKAN
- Original Message -
From: "Martijn Tonies" <[EMAIL PROTECTED]>
To:
Sent: Thursday, September 22, 2005 11:25 AM
Subject: Re: good database design
Hi,
Please re
Hello Tim,
> I disagree completely.
>
> I prefer to have regard to the statement of requirement, which in this
case
> is a concern over performance. If following conventional design rules
> creates performance issues, then performance related issues come first
when
> considering design.
Given tha
Hi,
Please reply to the list and not to me personally only.
> I want to explain my condition. I have a web site that habe 110onlne users
> at same time. But cpu usage is 2.00/2.00 (p4 3.0ghzHT)
> I think my database design is horrible because of this high cpu load.
Did you do an analysis to come
customers happy.
Tim Hayes
MYdbPAL - www.it-map.com
-Original Message-
From: Martijn Tonies [mailto:[EMAIL PROTECTED]
Sent: 22 September 2005 09:02
To: mysql@lists.mysql.com
Subject: Re: good database design
> I need links about good database design information for high loaded
> I need links about good database design information for high loaded web
> sites...
A database design should start with the logical data-related requirements,
not with performance related issues.
IMO, of course.
With regards,
Martijn Tonies
Database Workbench - tool for InterBase, Firebird,
13 matches
Mail list logo
