<mchi55@hotmail.com> wrote in message news:1158906861.665203.249420@e3g2000cwe.googlegroups.com...
>I have a table with 220000 rows.
>
> There is a column called status_id. I have a nonclustered index on
> statusid.
>
> if I do a
>
> select from table
> where status_id = 161
>
> I get a table scan with the non clusteredindex.
> There are about 16000 records with a status_id of 161. This there no
> way to avoid the table scan since there are so many records? Why is
> it not using the index?
> select *
> where status_id = 161 also takes like 2 minutes to run.
>
> If I place a clustered index on status_id...the query returns in a
> split second and uses a clustered index seek.
> For production purposes...I can't place the clustered index on
> status_id.
>
> What can I do?
>
> Also...the table has about 200 rows...completely unnormalized and a
> mess.