Jeff Moden (7/28/2014)
From the article:
However it's usually not your company, and it's not your place to prove that there is a flaw in a system. It's especially true that it's not your place to prove things without having been given permission to do so. Proving a point on your own is something children do, not professionals.I totally disagree as written above especially when it comes to private information such a Social Security Numbers. It [font="Arial Black"]MUST [/font]be proven if it exists and action must be taken. I consider it to be one of those unwritten laws that is the responsibility of every IT worker.
I'm gonna take this from a different angle. I agree with Jeff that it is your responsibility. If there is a critical flaw that could cause serious errors, cost the company big money, or even place peoples lives at risk - it is your right and responsibility to say and do something about it.
How you go about proving the flaw is a different story. Proving the point can be as simple as providing visibility via reports that are already being run or that were to be implemented anyway.
If there is a serious design flaw in the braking system of that new car - you need to say something about it instead of letting it go to production where lives are in danger and excessive cost to the company will occur.
If the use of nolock could cause a double dose of morphine to be given (or no medication given at all), then it is your responsibility to raise that concern and prove that nolock could cause those funky results.
Just because you are proving something doesn't mean you have to be a putz about it. And when you are right, act like you've been there before - don't gloat.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events