No perceived improvement even after adding index
To try to improve performance, I added an index to an exisitng query which did a clustered index scan (table scan) and a sort. I added all the columns required by the query including the sort columns in the correct sequence. Now the query uses that index, but still does an index scan and not a seek on the status field. It also does the sort. I was hoping to gain some performance but I think not. What all am I missing here and doing wrong. Please help.
Table and index are here.
This index would get rid of the sort, but I suspect it will still use a scan:
CREATE UNIQUE NONCLUSTERED INDEX IX_LAScheduleInventoryBuild ON dbo.LAScheduleInventoryBuild(StartHour, StartMinute, Status) INCLUDE(WebServiceUrl) WITH (DROP_EXISTING = ON);
Whether that's a useful or optimal index for the rest of your workload, not sure. A filtered index may be useful as well, if <> x is consistent.