March 11, 2009 at 12:28 am
March 11, 2009 at 1:02 am
A index scan is usually bad. But a book mark lookup is indicating that you don't have enough covering index for your query.
If you can attach your sql script and a SQL Plan that will be helpful ...
Thanks.
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 11, 2009 at 1:15 am
How long does the query take to run?
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
March 11, 2009 at 3:15 am
March 11, 2009 at 6:20 am
Post table definitions, index definitions and execution plan (saved as a .sqlplan file, zipped and attached)
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
March 11, 2009 at 6:26 am
Hi,
As Gail has suggested, please post your execution plan.
At first glance it would seem that your query could benifit from additional indexes being added to the tables involved in your query.
Cheers,
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply