Home Forums Database Design Design Ideas and Questions Database design RE: Database design

  • November 26, 2007 at 8:57 am

    #754106

    3 rd normal form

    (or)

    What's the database for?

    What's going to be stored in it, for how long and why?

    Who's going to be using this and how?

    (or)

    both

    Both... you cannot design a database in correct 3rd normal form without knowing the rest "what's going to be stored in it".

    The "how long" and "who's going to be using this and how" actually doesn't matter much. Whether it's for a GUI or Batch File processing doesn't matter because it should always be able to do both.

    If you're talking a "data mart", then that's something different. Frequently, they are both pre-summarized and somewhat "de-normalized" for performance reasons.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)