• kelly.bailey (7/13/2015)


    I know this was a re-run of an old editorial, but...

    How should people be using data? In general:

    1) Big important strategic decisions should be made using long-term data that is carefully analyzed. Although such decisions can be time-sensitive, the need to make them is (or should be) known in advance. If senior leaders are looking ahead as they should be, there should (usually) be enough lead time to say, "Get the database back up for operational needs first."

    2) The kinds of decisions that require real-time information are more of the day-to-day operational. If people rely on the database to make such decisions, downtime is the killer. Incomplete data is no big deal, if the immediately essential data is available and accurate.

    3) Assuming we have good historical data, the laws of statistics tell us that a relatively small number of recent datapoints shouldn't change "the big picture" signficantly - and if they do, then yesterday was probably just an outlier and we shouldn't conclude much from it.

    Henry Ford reputedly said that if he'd asked his customers what they wanted, they'd have said a faster horse. And unfortunately, in real life, leaders aren't always looking ahead as they should and they don't necessarily understand significance or good decision-making. So in a sense, it becomes a question of whether we're going to try to understand our customers' needs enough to actually help them, or if we're going to be co-dependent "enablers."

    Heh... again, no one misses data until it's not available. And, statistically speaking, if someone loses data about my paycheck, taxes, hours worked, stocks, mortgage payments, etc, etc, then there will be a very high probability that I'll pull the Dunkin' Donuts move on them... "See you in court, sonny".

    Mind the pennies and the dollars will take care of themselves. 🙂

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