http://www.sqlservercentral.com/blogs/sql_awesomesauce/2010/09/29/how-to-prove-a-fact-_2800_again_2900_/ Printed 2017/05/26 09:24AM
How to Prove a Fact (Again)
Sean’s latest rant – about a vendor with a dangerously small amount of SQL knowledge – has spurred me to talk about a common theme I’ve been seeing lately: Proving facts to ignoramuses*.
How to Prove Facts to the Unbeliever
- State the fact.
- Explain the fact.
- Restate the fact. [Realize here that they won't listen to a thing you say, even if you show them.]
- Go find indisputable industry experts (product documentation from the owning company, testimonials and blogs from members of the development team, and/or clearly documented tests with results).
- Email it to the unbeliever, copying his boss and everyone who was in earshot of the original dispute.
- In the email, prominently mention your credentials to really put the slam on the infidel (10 years in the industry, certifications, MVP, articles and books you’ve written on that subject, the fact that you wrote THAT PARTICULAR PIECE of the SQL engine, status as owner of Microsoft itself, omniscience, etc. as appropriate).
- Perform the victory dance of your choice.
Note on step #6: Establishing your credibility never works as an opening gambit. You could be the internationally recognized reincarnation of the Buddha of database administration (whoever that might be), and some jackass will still say “Yes, but you just don’t UNDERSTAND high availability like I do…”
Proofs to Recent, uh, Arguers
Backup operations DO NOT CAUSE BLOCKING. Citation: Paul Randal, A SQL Server DBA myth a day: (30/30) backup myths
Using NOLOCK as a first response to poor query optimization…IS BAD. Citation: SQL Server Books Online, Table Hints
Cursors ARE WAY WAY WAY SLOWER THAN SQL STATEMENTS. Avoid them. Citation: SQL Team, Cursors: An Overview
* (Crapola, I wonder if there’s a proper spelling of “ignoramuses”…)