• Yakov Shlafman (3/18/2010)


    SSChampion, why we do not question the fact that in production environment

    we have garbage - garbage database design, garbage data, garbage applications that produce garbage results.

    Before that garbage went into production customers signed it, QA signed, Developers and DBA got paid

    fat bonuses. And here I am changing 29 by 28.

    But I do agree with everything you said and our emotions should not always drive us.

    Thanks for your comments.

    Again there are so many issues (not always technical)

    I would like to discuss and hear others opinion especially from SMART people like you.

    Regards

    I absolutely agree with that. Why [font="Arial Black"]DOES [/font]production data have garbage in it!!!! And I also agree that the bums who designed a system to allow such garbage shouldn't have ever received a paycheck never mind a fat bonus.

    However...

    I think you're being sarcastic when you say that you like to "hear others opinion especially from SMART people like you." Let us truly consider why the database has garbage in it. Could it be that a bunch of people with the same attitude (or lack of) towards the sanctity of the data as what you stated in your article wrote the database?

    There's another aspect to some of these "urgent ad hoc reports" that people don't consider and that I've been privy to a couple of times now. You flat out don't know what the report is for. In fact, your manager may not know what the report is for. (S)he may have been directed to have his/her people produce the report and it could be for something like a police investigation to determine who possible suspects are based on their last charge date. Your willy nilly and thoughtless change may have either put an innocent person in harms way or may have kept a guilty person from being considered because it may have been the year or the month that was in error and not the day. You should have reported the discrepancy instead of taking matters into your own hands.

    If you're going to be a data professional, then be professional even if you think you're an underpaid professional. Like I said, data isn't the only thing that's supposed to have integrity.

    And drop the bit about emotions driving this... I'm not the one that decided to get sarcastic here.

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