Blueprint
In 2016, we got the STRING_SPLIT function. That was nice, because prior implementations had a lot of problems
But out of the gate, everyone looked at what we got and couldn’t figure why this would drop without a column to tell you the position of each element in the string.
Recently I updated SSMS to 18.10, and went to work on a couple scripts that use STRING_SPLIT.
I was immediately confronted by a bunch of RED SQUIGGLY LINES.
Why?
Not Yet But Soon
Huh.
Insufficient! You’re insufficient!
Oh, enable_ordinal. Neat.
At least it’s a bigint.
Thanks for reading!
Going Further
If this is the kind of SQL Server stuff you love learning about, you’ll love my training. I’m offering a 75% discount to my blog readers if you click from here. I’m also available for consulting if you just don’t have time for that and need to solve performance problems quickly.
Related Posts
- Things SQL Server vNext Should Address: How Did I Do?
- Things SQL Server vNext Should Address: Add Lock Pages In Memory To Setup Options
- Things SQL Server vNext Should Address: Add Cost Threshold For Parallelism To Setup Options
- Things SQL Server vNext Should Address: Make Dynamic SQL Easily Traceable
👏👏
curious does this ever give the incorrect ord?
select value, ord = row_number() over (order by (select null)) from string_split(‘1,2,3’, ‘,’)