• jay holovacs (10/3/2011)


    While risk taking is a psychological characteristic, many people including myself, avoid random risk taking, but will take selected risks (Steve might know about about the back road to Hurricane Pass where the wheels of my Jeep were literally inches from a couple thousand foot drop).

    The same applies to systems we run. I am in NO hurry to move stuff off of one database platform that is working just fine onto another unless there is a direct benefit to doing so (like end of support). There are enough unpredictable variables in life, introducing extra ones withoug significant payback I think is counter productive.

    Of course not... that's why backups would be done everyday. The point that I'm trying to make is that the backups from a system migrated to 2k8 don't work on 2k5 and extraordinary steps must be taken to preserve the data in a 2k5 environment "just in case". All of that isn't worth the risk of doing the migration to 2k8. That's all.

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