• Try this then:

    DECLARE @FILTER VARCHAR(8000) = 'MGR1,MGR2'

    SELECT *

    FROM dbo.EMPLOYEE AS EMP

    WHERE EMP.MGR IN (SELECT Item FROM DelimitedSplit8K(@FILTER, ','))

    You can find the DelimitedSplit8K FUNCTION here:

    Tally OH! An Improved SQL 8K “CSV Splitter” Function[/url]

    Note that DelimitedSplit8K is designed to work with VARCHAR(8000) and not NVARCHAR(MAX) as in your original code. You'd need to either modify it to use that data type (not recommended by the author) or use a different delimited string splitter. Unless you need the UNICODE characters, it's pretty unlikely the user would enter a 2GB parameter string.


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    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