Post reply

Help me in designing table and its indexes

  • March 6, 2018 at 5:44 pm

    #1982174

    RonKyle - Tuesday, March 6, 2018 10:11 AM

    While there's always an exception, I've not yet seen where separation to multiple tables actually solves anything such as what the OP has portrayed except to justify the need for additional disk space, CPUs, and Developer time

    Wasn't saying you were wrong, was just saying more information was needed.  I ran into the street number/street name issue when I was first learning SSAS and created a data warehouse for my daughter's Girl Scout cookie sales.  To determine the percentage of houses sold to versus the overall number I had to break out the addresses further.  But it made me realize that a realtor or the USPS might also have the same need.  But of course generally these are in a single column because in most databases they can be considered atomic.  But since then I've always kept in mind the reporting goal, and sometimes that changes the way the database is designed.

    Yep... understood.  Probably a misunderstanding on my part but I thought you were saying that separating house numbers into one column and street names into another column justified the recommendation for separating managers and employees into two separate tables.  Just wasn't seeing the connection there.

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

Viewing post 16 (of 15 total)

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