Thanks, Vladan, I remember what it was now. It was LIKE and IN, IIRC, that forced a table scan. My bad. I blame it on being sick since last Wednesday....
Sorry, I don't have a quick answer for what you're looking for. All I can suggest is that there is a world of information looking at the system tables and...
I recall having read that using BETWEEN automatically forces a table scan. I don't recall where, but I'd break it up using two >= and <= statements and see if...
Indexes were also my first thought. Check to see that your indexes are built well (logically) and that whatever stored procedures are accessing them are actually hitting them through SQL...