Kirk,

I'm afraid these WITH queries you have are outside my area of expertise. Is the TOP 1 with no order by causing it to use the roomname index?

>When looking at the execution plan, it shows a index scan on coRooms.RoomName as is costing 41%, I'm assuming it is from this part of the query (really a subquery in the main query).
>
>The coRooms table as a clustered index on the the RoomID (PK), as well as a normal index on deptID and RoomName (seperate indexes).
>The meetings table as a nomral index on RoomID
>
>Any idea's how to get the query to perform a seek vice scan?