Howdy!

"normalization can lead to worse performance" is a useless statement. Normalization can also lead to better performance. It *does* lead to more robust data models that more clearly communicate their design.

Deciding not to normalize amounts to denormalization.

Making that decision for "performance" implies that the normalized form has performance issues. Without normalizing and testing, you cannot properly assess the differences. You end up making assumptions about where to optimize, and those assumptions tend to be dead wrong too much of the time.

Further, what do you mean when you say "consider using a search engine"? The data being described seems to be live data that will be updated transactionally. That need points toward more fully normalized forms, but it is not clear how the balance between update activity and query activity lies. A "search engine" is no help for modifying the data, and may be counterproductive if you have to frequently query rapidly changing data.

yours,
Michael

In reply to Re^4: (OT) Couple of Data Model Design Considerations by herveus
in thread (OT) Couple of Data Model Design Considerations by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.