The new info is from the SP...The batch uses a DIFFERENT plan. An index seek on the index I had set up.

Identical params and tables. In fact, the SP is identical to the batch with the exception of the Declares for variables used as params. That's why this is weird.

>>New info:
>>
>>According to the execution plan it is performing a clustered index scan on the DB tables and returns ALL of them. This is my bottleneck apparently. Should I use a join hint or some other mechanism?
>
>Are you running SP and batch against the same data?