yes I know, but some clients still use version 2012... so I cannot use it
If you want the quickest fix just add OPTION (MAXRECURSION 1000) to your select query.
If performance is an issue then Eirikur's code will be much faster and works with SQL 2012.
I guess I'd never recommend trying to fix the recursive method.
It's a little like choosing to use this for a few hazel nuts.
Mate, you owe me a keyboard π
π
Luckily, my laptop is "beerproof"
That seemed it was meant to be a sledgehammer to crack a nut joke. But I don't see how it relates to this? What's the sledgehammer? Surely not a weakly performing rCTE?
The sledgehammer is the rCTE, and you are being very gentile using the word "weakly" here, which translates to "poorly" even if done "weekly"π
π
It still drive me bonkers, how many are using sub-optimal code for such a common thing as splitting DSV/CSVs.
Chris's post just mate me laugh when having a mouthful of a beautiful aleπ
Stop it, you're making me thirsty!
Abbot ale, absolutely beautiful:laugh:
π
When are we meeting up next? I'll be happy to quench your thirst.
Sooon!!
I'm snowed under π I'll be in touch when I can punch an arm through it.