Table.Field method

[Ruslan Zasukhin]

On 7/6/06 11:30 AM, "Joakim Schramm" <joakim at astrocalc.com> wrote:

>>> 
>>> Just a design question, is it a bad idea to have 1 table with many
>>> fields or better to split them up in several tables, I am mostly
>>> thinking of performance?
>> 
>> Valentina prefer tables with smaller number of fields.
>> 
> Any preferable max number 10, 20, 30 etc. to not significantly "loose" in
> performace"?

You see, exist 2 kinds of performance.

1) Performance of INSERT/UPDATE/DELETE
2) Performance of SEARCHES.

When you work with any db you always make trade of between these ..


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]