>>

>>SELECT Table.FirstName
>> FROM Table
>> WHERE Table.PrimaryKey in (1,2,3,4)
>>

>
>Yes, this is exactly what I am looking for. As a mattter of fact, I just found it at the same time.
>
>Would you know if this would be as good for the execution plan or performance could be an issue?

Always depends on the data at hand, but most uniform best times should be reached by piping the list of PK's into a temp table with index and inner joining to base select table, esp on longer PK-lists.