• Here's another way that doesn't worry much about how many spaces are included.

    WITH SampleData (Condition, Columnname) AS

    (

    SELECT 'akraft,crunckel','TN'

    UNION ALL SELECT 'AL,AZ','State'

    UNION ALL SELECT 'Atlanta,Austin-San Marcos','MAC'

    UNION ALL SELECT 'aney,aventura','Area'

    UNION ALL SELECT 'Alexandria, VA,Arlington, TX','Market'

    UNION ALL SELECT 'Alpharetta,Alexandria','City'

    UNION ALL SELECT '001,002','StoreS'

    UNION ALL SELECT 'SameStore,HeitmanI','Store Type'

    UNION ALL SELECT 'InLast6Months,CS-CC','Space Types'

    ),

    SplitStrings AS

    (

    SELECT *

    FROM SampleData

    CROSS APPLY dbo.PatternSplitCM(Condition, '[, ]')

    )

    SELECT Condition, ColumnName

    ,NewCondition=

    (

    SELECT CASE [Matched] WHEN 0 THEN ''''+Item+'''' ELSE ',' END

    FROM SplitStrings b

    WHERE a.Condition = b.Condition AND a.ColumnName = b.ColumnName

    ORDER BY ItemNumber

    FOR XML PATH('')

    )

    FROM SplitStrings a

    GROUP BY Condition, ColumnName;

    PatternSplitCM can be found and is explained in the 4th article in my signature links.


    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