Home Forums Database Design Design Ideas and Questions Avoiding the Deep model (Key, value) RE: Avoiding the Deep model (Key, value)

  • August 30, 2012 at 7:51 pm

    #1532178

    mishka-723908 (8/22/2012)

    The value data-type in this case will always be the same. I did not think using EAV, but several developers here thought that we should. Thank you everyone for your comments.

    To be honest, we don't actually have enough information to recommend or condemn because you haven't told us what the table is designed to hold, what the column names and purposes are, nor why you might want to eventually add a column or two. Some information in that area would certainly help us help you.

    I'll join the others in saying that an EAV or NVP will most likely cause you some huge problems but, again, there's just not enough information to tell. It may very well be that an EAV or NVP is exactly what the doctor ordered (I stess again... probably not).

    For example, it would be a huge benefit to you to use an NVP to store monthly data rather than storing monthly data in separate columns.

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