• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 292
  • Last Modified:

removing the Key lookup increased the reads.

I have added a covering index which removes a Key Lookup. The Cost on the query plan has been reduced from 85% key lookup to 7% covering index.

However, the number of reads went up from 2786 to 2846.

Is this ok?
0
Mr_Shaw
Asked:
Mr_Shaw
1 Solution
 
knightEknightCommented:
If it performs noticeably better, then I'd say it's okay.  :)
0
 
Mr_ShawAuthor Commented:
thanks
0
 
lcohanDatabase AnalystCommented:
The following link explains you why the reads may be higher but basicaly knightEknight is right - you should look at the query from best performance point of view nut just how many (logical) reads are done.

You can use set statistics IO on; and set statistics time on; to find out more about your query.

http://blogs.msdn.com/b/craigfr/archive/2006/06/30/652639.aspx
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now