No it is not on lessthan.... check SQLServerCentarl.com.
>Hi Cetin,
>
>Where is the link to the original code by Jeff Moden? Are you referring to the numbers table idea of splitting the list?
>
>See also http://blogs.lessthandot.com/index.php/DataMgmt/DataDesign/the-ten-most-asked-sql-server-questions--1#3
>
>>>Struggling with t-SQL syntax to get a set of record by passing in a string built in vb .net from a list of primary keys. Need 2 versions - one for integer keys, one for guid / uid keys
>>>- I can be flexible about what and how I pass the params
>>>I understand t-sql does not actually have arrays so my first instinct is to pass in a string with the guids delimited with ' and separated with a comma and see if the pk is in the "list" of the string.
>>>
>>>But that won't work with
>>>
>>>select * from members where cpk in (@pklist)
>>>
>>>if I leave out the delimeters and have a single string with single quotes surrounding it the above select works but only pulls the first record
>>>
>>>Integers an even bigger disaster as they a string values and the above code doesn't cast them
>>>
>>>Plan B would be to build a table from the incoming param string and join against that to get the recordset but the syntax for that is beyond my t-sql skills
>>>
>>>Have a feeling somebody has the answer to this
>>>
>>>Guidance appreciated
>>>
>>>TIA
>>
>>Jeff Moden's code is the best code I have ever seen about sending and splitting a comma separated list. You can find a modified implementation on:
>>
>>http://www.foxite.com/archives/sqlexec-with-a-local-cursor-0000192577.htm
>>
>>It doesn't have 8000 characters limit and it does work with too many items in the list.
>>
>>An alternative is to use Linq:
>>

>>List<int> cpk = new List<int> {1,3,5,6,....};
>>cpk.Add(...);
>>
>>var members = from m in db.Members
>>                      where cpk.Contains( m.memberId )
>>                      select m;
>>

It is fast and IDs are sent as parameters. Drawback is that parameters are limited to 2100 (but that shouldn't be a problem if you can use splitting algorithms that use varchar(8000) which even wouldn't let you create 2100 IDs).
>>
>>If you have SQL 2008, then of course sending a table is a nice solution.
>>
>>Cetin