Home Forums SQLServerCentral.com Editorials Undocumented Routines: Forbidden fruit. RE: Undocumented Routines: Forbidden fruit.

  • February 1, 2009 at 7:00 pm

    #936217

    ALZDBA (2/1/2009)

    Jeff Moden (2/1/2009)

    And THAT is what I'm really getting at... it doesn't matter if it's an undocumented feature or not! If you don't do any regression testing before you drop a "fix", sp, or whatever into your production system, you're begging for "Death by SQL" even if you haven't used any undocumented features.

    It's not the use of undocumented features that will kill you... it's any change even on fully documented features. You must test before making any patch or sp to SQL Server or at least be very, very aware of what the impact will be.

    Indeed, you cannot effort not to do an acceptable series of regression tests.

    But by using undocumented features, you will get into troubles in the long run, and it's removal or alter will not be nor get documented or announced.

    My point is, that also happens with fully documented features.

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