Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a SQL statement (that I can’t post here). When I look at its execution plan I see most of the time is sitting in sorts, followed by index scans.
Is there anything I can do to lessen the time spend on sorts? an index of any kind? Anything I can do to lessen the time spent in index scans?
Clustered index scan is essentially a table scan, where every row in the table is being examined.
You’re probably missing an index on that table for this query… look at the fields that you’re filtering by / joining on, and add indexes to these columns.
These indexes will also likely prevent the nested loop / sort operations as well.