• seebert42 - Monday, August 14, 2017 5:17 AM

    Wow, a four year old rerun.  I now understand an interview I had two years ago better.  I left that interview feeling like I was a bad fit for a manager who did not understand the evolution of the stream.

    For a senior level DBA, performance optimization is the pinnacle of the art, and I would start there.

    "It Depends" on the type of DBA that you're looking to hire.  Although I agree that performance optimization is incredibly important for the system, it may have absolutely nothing to do with what the job description is for the "DBA" position.  You also need to define what "performance optimization" is.  Some think that it's setting up SQL Server with the right Trace Flags, the correct number of TempDB files, and deciding which type of RAID should be used for which drives and possibly include some form of DR replication that keeps the RPO very high and the RTO very low.  Others think that it's finding and fixing performance challenged code.  Some include the "pipe" itself.

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