October 5, 2011 at 6:05 am
I am looking for a bettwer way to explain this to my partner in crime who just doesnt get it. Which is a better thing and why?
Kindest Regards,
David
** Obstacles are those frightening things that appear when we take our eyes off the goal. **
October 5, 2011 at 6:08 am
What did you say to him?
October 5, 2011 at 6:20 am
have you tried using the phone-book anaolgy?
October 5, 2011 at 6:22 am
I have used many types of analogies. A phone book wasnt one of them. I am not looking to re-hash what I have done. I am looking for a new way to get the point across to a doorknob. :: grin ::
Kindest Regards,
David
** Obstacles are those frightening things that appear when we take our eyes off the goal. **
October 5, 2011 at 6:26 am
I'm asking what you gave to him so that I can fill in the blanks or edit an analogy.
I'm notlooking to spend 3 weeks writing a full book to re-explain this for you.
October 5, 2011 at 7:34 am
http://sqlinthewild.co.za/index.php/2007/11/15/execution-plan-operations-scans-and-seeks/
http://www.sqlservercentral.com/articles/Indexing/68439/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 5, 2011 at 7:35 am
Scans aren't necessarily bad and seeks aren't necessarily good. It really depends on their relationship to the rest of the process, the number of rows involved, joins associated... It's actually not a simple story to tell. But in general, it's got to be easy to understand. Looking up the index to find something versus rereading the entire book.
"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
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply