With enough qualitative feedback, they may actually consider making some of these enhancements: Please help with STRING_SPLIT improvements.I have asked for the community's help in improving the built-in function here: In other words, if you pass in 3,6,1 the result will likely be in that order, but it could be 1,3,6. You can't do this with just the native STRING_SPLIT function added in SQL Server 2016, because there is no guarantee that the output will be rendered in the order of the original list. You could also add the idx you want as an argument to the function, but I'll leave that as an exercise to the reader. Sample usage: SELECT Value FROM dbo.SplitString('foo,bar,blat,foo,splunge',',') RETURN ( SELECT, idx = RANK() OVER (ORDER BY n) FROMįROM (SELECT Number = ROW_NUMBER() OVER (ORDER BY name)
A set-based approach will be superior, I promise, if you can use a delimiter other than a space: CREATE FUNCTION VARCHAR(255) Most of the solutions here use while loops or recursive CTEs. This version takes care of the limitation: create function char(1)
Previous version would fail for input string longer than 4000 chars. select sįrom dbo.SplitString('Hello John Smith', ' ') Then, use it as any table (or modify it to fit within your existing stored proc) like this. First, create a function (using CTE, common table expression does away with the need for a temp table) create function char(1)
0 kommentar(er)
