STRING_SPLIT()

Question

STRING_SPLIT()

Steve Jones - SSC Editor

SSC Guru

Points: 736478
More actions
July 7, 2018 at 11:21 am

#407139

Comments posted to this topic are about the item STRING_SPLIT()

Viewing 15 posts - 1 through 15 (of 23 total)

You must be logged in to reply to this topic. Login to reply

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 1

Steve Jones - SSC Editor - Saturday, July 7, 2018 11:21 AM
Comments posted to this topic are about the item STRING_SPLIT()

I don't know what went wrong. I clicked on the correct answer and it said I was wrong and it cited one of the other answers in the explanation.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Eirikur Eiriksson SSC Guru Points: 182915 More actions · Answer 2

The alleged "correct" answer is wrong.
😎

What version of SQL Server did you test this on Steve? Looks to me that there must be an implicit type conversion on the delimiter parameter.

Jeff Moden SSC Guru Points: 1004406 More actions · Answer 3

Eirikur Eiriksson - Sunday, July 8, 2018 12:45 AM
The alleged "correct" answer is wrong.
😎
What version of SQL Server did you test this on Steve? Looks to me that there must be an implicit type conversion on the delimiter parameter.

Lordy... I have to answer these things when I'm sufficiently caffeinated. I didn't read what the post thought was the correct answer, which is patently incorrect thanks to the space in the delimiter and, yes, I did click the correct answer... not what the post thinks the correct answer is.

I don't care about the points (never did) but, as Eirikur states, the alleged correct answer isn't correct and needs to be repaired.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Eirikur Eiriksson SSC Guru Points: 182915 More actions · Answer 4

Jeff Moden - Sunday, July 8, 2018 7:27 AM
Eirikur Eiriksson - Sunday, July 8, 2018 12:45 AM
The alleged "correct" answer is wrong.
😎
What version of SQL Server did you test this on Steve? Looks to me that there must be an implicit type conversion on the delimiter parameter.
Lordy... I have to answer these things when I'm sufficiently caffeinated. I didn't read what the post thought was the correct answer, which is patently incorrect thanks to the space in the delimiter and, yes, I did click the correct answer... not what the post thinks the correct answer is.
I don't care about the points (never did) but, as Eirikur states, the alleged correct answer isn't correct and needs to be repaired.

I use this to get properly caffeinated before responding to anything in the morning
😎
DeLonghi Dedica Espresso and Cappuccino Machine

Takes about 3-4 single espressos in about half an hour but then nothing can put one to sleep for the next 18-20 hours 😀

Just as Jeff said, this is not about any points, it's all about retaining the good quality of advice provided by the SSC community and this website.

Evgeny Garaev SSCertifiable Points: 7428 More actions · Answer 5

The second parameter is not acceptable - https://docs.microsoft.com/en-us/sql/t-sql/functions/string-split-transact-sql?view=sql-server-2017

SADSAC SSCrazy Points: 2411 More actions · Answer 6

and here i thought - am i losing my marbles?
the space after the coma in the delimiter will surely cause an error...
glad i'm not the only one who thinks the "correct" answer is actually incorrect...

Louis Hillebrand SSCarpal Tunnel Points: 4982 More actions · Answer 7

Didn't have any coffee yet, but selected the right (wrong) answer..

ako58 SSCarpal Tunnel Points: 4032 More actions · Answer 8

DECLARE @cars VARCHAR(200) = 'Porsche, Ferrari, Bentley, Jaguar,Range Rover'
SELECT *
FROM STRING_SPLIT(@cars, ', ')
please, remove last blank from separator

Mauricio_ SSCrazy Points: 2935 More actions · Answer 9

Right answer is an error. Problem is the space after the comma in the function. I want my point back! 🙂

Ed Wagner SSC Guru Points: 287026 More actions · Answer 10

Yep - at least everyone else saw the same thing I saw. Incorrect answer marked as correct.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

SW Skeen Mr or Mrs. 500 Points: 547 More actions · Answer 11

SW Skeen

Mr or Mrs. 500

Points: 547

July 9, 2018 at 6:38 am

#1996770

Too early on a Monday for this.

George Vobr SSChampion Points: 10009 More actions · Answer 12

I can not run the code, the article "Splitting Strings in SQL Server 2016" explains this differently.

Kaye Cahs SSCarpal Tunnel Points: 4135 More actions · Answer 13

Yeah, yeah. The correct answer is "wrong".

But more importantly, what is it that you don't want to do, Steve?

Raghavender Chavva SSCrazy Eights Points: 8669 More actions · Answer 14

When I executed this code in SQL Server 2016, below is the error:

Procedure expects parameter 'separator' of type 'nchar(1)/nvarchar(1)'

Thank You.

Regards,
Raghavender Chavva