Post reply

hi

  • July 18, 2011 at 5:29 am

    #241658

    high normalize or less normalize what will u put on ur database design in sql server ?

  • July 18, 2011 at 6:57 am

    #1354204

    sonwane.pratibha (7/18/2011)

    high normalize or less normalize what will u put on ur database design in sql server ?

    "It Depends"... is it a "real" database, a "reporting database", or a "data warehouse" database?

    --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)

  • July 18, 2011 at 7:11 am

    #1354211

    if it is a dataware house database

  • July 18, 2011 at 8:50 am

    #1354275

    How about normalize appropriately?

    For a datawarehouse? I'd suggest looking at a star schema. I'd consider that normalized, but not necessarily in third normal form.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • July 18, 2011 at 9:25 am

    #1354294

    Thanks !!!

  • July 18, 2011 at 1:49 pm

    #1354473

    As a general rule aim to be in at least Boyce-Codd / 5th Normal Form unless and until you find good reasons to do otherwise. That's the best way to ensure data integrity, avoid query bias and support future requirements/evolutionary schema changes. All of those are especially important in a data warehouse.

  • July 18, 2011 at 1:58 pm

    #1354479

    David Portas (7/18/2011)

    As a general rule aim to be in at least Boyce-Codd / 5th Normal Form unless and until you find good reasons to do otherwise. That's the best way to ensure data integrity, avoid query bias and support future requirements/evolutionary schema changes. All of those are especially important in a data warehouse.

    But keep in mind that 3NF usually is 5NF, and don't sweat the differences till they matter. And that warehouses usually do much better in formats other than 3NF, et al.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply