Phil Parkin (10/9/2015)
I found a 'GetNumbers' function here [/url] and that, when combined with Jeff's function, allows you to take the CLR out of the equation ... at least for the data you provide.
Phil - I don't think it's the CLR that's causing the problem. I only mentioned I figured that it would make it difficult for answers to replicate the function in their own test environment. The index error appears to be balking at the splitter function, not the CLR.
The real question in my mind, why is the function coming into play at all when the column values are persisted?
What's the point in persisting a value if SQL Server is going to ignore the value and recalculate it on the fly every time it's included in a query?