• David.Poole - Sunday, September 23, 2018 5:40 AM

    The ridiculous thing is that the cost of peoples time arguing why you shouldn't have a RAM upgrade far exceeds the cost of that RAM upgrade.
    The cost of nursemaiding a system with insufficient RAM will exceed the money "saved" by many multiples.

    To Jeff's point on fixing code, new revenue generating opportunities always win out over cost saving tasks.  Tech debt fixing is cost saving.  That said, I don't get why the reaction to asking for stuff to be fixed is akin to that observed when baptizing a cat

    Heh... SPOM!  ROFLMAO!  I got a real live picture of the baptizing a cat thing... and it's an accurate portrayal.  I'm definitely going to use than analogy in the future. 😀 

    And I totally agree.  While having a decent amount of RAM and headroom on the disks (physical or SSD) may not be the ultimate solution to performance problems, it DOES make life a whole lot easier.  A great example of that is it allows me to rebuild a 500GB Clustered Index without blowing out the MDF file because I asked for and got a 1TB "DBA work disk" (which will NEVER contain anything permanent).  Very justifiably, I knew that they were going to want to know how I was going to use it and what the ROI was going to be in some detail but I provided that without being asked.  That's the key for most people in charge of the purse strings.  They don't want to hear empty/non descript garbage about "Best Practices", etc.  They want something in writing that explains the benefit to the company both in the short term and, especially, in the long term even if they may not understand the nitty-gritty technical stuff.  It also helps if you can "bring it down to their level of understanding" without it making is sound like you're belittling their possible lack of knowledge on the given subject.  There is a bit of an art in making such requests palatable and well thought out because a lot of people think that IT people just want to live up to "He who dies with the most toys wins" attitude that so many people to put up without providing and adequate ROI.

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