Timeline for SQL Server execution plan is using PK instead of index
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2015 at 21:28 | answer | added | gbn | timeline score: 3 | |
| Oct 7, 2015 at 20:36 | comment | added | juliano.net |
Just the [Id] column.
|
|
| Oct 7, 2015 at 20:35 | comment | added | Jeffrey Van Laethem | What columns exactly does the PK consist of? | |
| Oct 7, 2015 at 20:20 | comment | added | juliano.net | What do you suggest me to change so I can improve this query? The Project table has only 27k rows, I don't understand why such query is taking 5 seconds to run. | |
| Oct 7, 2015 at 19:05 | comment | added | a1ex07 | It seems to me that index on Company_Id is not selective enough, and optimizer decides that full table scan (clustered index scan) is cheaper than index range scan + lookup. | |
| Oct 7, 2015 at 18:55 | history | asked | juliano.net | CC BY-SA 3.0 |