comma separate value show as table

Question

comma separate value show as table

Viewing 2 posts - 16 through 16 (of 16 total)

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

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

I do need to make a correction to my last. It's not "non-Latin" collations that may have the problem... its usually the "Windows Collation" compared to "SQL Server Collations" that present the problem.

This subject has come up often enough that I wrote most of an "SQL Spackle" article on the subject last night. I'll polish it up a bit more and submit it tonight.

Thanks for the awesome question, Dwain.

--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)

Dwain Camps SSC Guru Points: 86908 More actions · Answer 2

Jeff Moden (8/20/2012)
I do need to make a correction to my last. It's not "non-Latin" collations that may have the problem... its usually the "Windows Collation" compared to "SQL Server Collations" that present the problem.
This subject has come up often enough that I wrote most of an "SQL Spackle" article on the subject last night. I'll polish it up a bit more and submit it tonight.
Thanks for the awesome question, Dwain.

Jeff - One of the great things about you is that you recognize when you are able to respond to the needs of the SQL community and don't hesitate to do so.

You'll need to keep us up to date on when this article is published. I suspect that information on this issue is scattered, so having a one stop reference will no doubt be a godsend.

Looking forward to this publication!

My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]
My thought question: Have you ever been told that your query runs too fast?

My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St