I was assuming you dynamically built the query in the front end so could handle splitting the items that are part of the IN clause.
Alternatively, something like this will also work.
DECLARE @UsersEntry VARCHAR(8000) = '83944, 83955, 83954, 83951,83947, 83946, 83953';
WITH UserParms AS
(
SELECT ItemNumber, Item
FROM dbo.DelimitedSplit8K(@UsersEntry, ',')
)
SELECT field1, field2, field3
FROM table
JOIN UserParms ON field1 = item
WHERE field1 IN (SELECT Item FROM UserParms)
ORDER BY ItemNumber;
DelimitedSplit8K[/url] can be found at the link.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St