I know this is an ancient post, however I came across it when searching for a way to get process information into SQL Server. This method is fundamentally flawed as...

Right, it shouldn't happen in a production database but will have to be dealt with during ETL processes, especially if you want to be able to report on such errors.

select STUFF(

(

SELECT ',' + StatusDesc

FROM MyStatusList

FOR XML PATH('')

ORDER BY Status_Id

),

1,

1,

''

)

ok... i loved the for XML path.

The stuff it's kind of cute, but i didn't understand TYPE... and the ./text thing... I have to study more.

Where can I learn more...

Problem with recursive CTEs is that they are very slow in comparison to the XML method.

Please see here[/url] for a much better article on the subject.

stuff((select ',' + ID

from teste

for XML path(''),TYPE).value('(./text())[1]','NVARCHAR(MAX)'

),

1,

1,

'')

This copes with any string length.