Re: Clues on modeling a really simple concept

In message
<28933dcc-983a-409f-b54e-4de451b46ffc_at_z15g2000yqm.googlegroups.com>, Spike <fauria_at_gmail.com> writes

>Hi!
>
>I was thinking about system performance vs. normalization. By adding
>that extra relationship, three-level joins can be avoided, and so
>stressing the dbms too much.
>
>Do you think is a good idea in general to denormalize the data model
>by means of performance?

If you need better performance then it's one way of getting it, but any move away from a fully normalised structure will cost you more time and effort in building the application and managing the data. In some situations the right answer is to denormalise. In other situations the right answer is to upgrade the hardware. In some other situations you might need to do both. But if you build the system using a fully normalised structure and users aren't complaining about performance then you don't need to do anything.

I suggest building the system using a fully normalised structure. Try that out on the users and see whether there are complaints about performance.

If users complain then you need to make some decisions. I can't make those decisions for you without a thorough analysis of your particular application, which I'm not going to attempt via Usenet. If you want me to do a thorough analysis we need to talk about my rates for consultancy.

-- 
Bernard Peek