• kiwood (9/26/2016)


    First, I agree that monitoring all the things that can go wrong should be done. And hiding things is generally a bad idea.

    But let me play a little devil's advocate here. I have seen bosses that would be asking about every little thing that might be indicated to be a problem. Such as that query that took a half second longer than the threshold. Or perhaps they would come into the office the moment page life expectancy dipped just a little bit. There are bosses which would constantly be bugging about every little noise made in the system.

    At one place I worked at, it took our new DBA (who was learning on the job) a couple weeks of tweaking to get a described tool to where it wasn't giving a regular stream of alerts. And this was on an instance that had been running for a couple years as it was. Which does bring up something - a tool that was described should be normal. And it should be properly setup for your installation. Perhaps it should have some different settings for different people. Some bosses will also always be constantly poking into things that they don't understand. Some will learn what to be concerned about, but not all.

    Absolutely true stuff. I've had similar issues with non-technical bosses. It just means you have to work hard to clarify the reporting and to communicate well with the person in question. It doesn't mean you literally hide bad things from them.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning