December 3, 2012 at 7:52 am
Jaroslav Pfauser (12/3/2012)
(0 row(s) affected)SQL2008 (64-bit) SP2
It seems you wrote a test script that did not cover the full range of possibilities. Include CHAR(198) and CHAR(230) in your test.
(2 row(s) affected)
December 3, 2012 at 8:51 am
SQL Kiwi (12/3/2012)
Jaroslav Pfauser (12/3/2012)
(0 row(s) affected)SQL2008 (64-bit) SP2
It seems you wrote a test script that did not cover the full range of possibilities. Include CHAR(198) and CHAR(230) in your test.
(2 row(s) affected)
Doesn't the test sql provided in answer already do that?
On my server it returns 0 rows, so it appears like some other things affect this. Maybe default collation. Probably.
December 3, 2012 at 9:13 am
On my server it returns 0 rows, so it appears like some other things affect this. Maybe default collation. Probably.
I'd suspect a different set of Extended ASCII characters, probably not the default collation on the server. For the folks who are getting no records back, what language is the machine running?
[appending] Yeah, it looks like several of the ASCII character sets don't include those AE/ae characters. http://en.wikipedia.org/wiki/ISO/IEC_8859
December 3, 2012 at 9:33 am
Great question...but a challenge for a Monday morning!
Rob Schripsema
Propack, Inc.
December 3, 2012 at 9:42 am
Very interesting question... definitely not something I would have realized otherwise.
December 3, 2012 at 10:56 am
Robert-378556 (12/3/2012)
SQL Kiwi (12/3/2012)
Jaroslav Pfauser (12/3/2012)
(0 row(s) affected)SQL2008 (64-bit) SP2
It seems you wrote a test script that did not cover the full range of possibilities. Include CHAR(198) and CHAR(230) in your test.
(2 row(s) affected)
Doesn't the test sql provided in answer already do that?
On my server it returns 0 rows, so it appears like some other things affect this. Maybe default collation. Probably.
Yes, the default collation. The test sql in the answer works where the default collation is one of the Latin1_General set, but for some other collations it doesn't. I should have specified a default collation for the context of the code as part of the answer. What 8-bit character char(I) delivers depends on the default collation for the context in which char is called, so that whether ascii(char(I)) = I (I a non-negative integer less than 256) depends on what I is and what the default collation is. Personally I think that's unfortunate, but that's how char operates.
Tom
December 3, 2012 at 11:10 am
Robert-378556 (12/3/2012)
SQL Kiwi (12/3/2012)
Jaroslav Pfauser (12/3/2012)
(0 row(s) affected)SQL2008 (64-bit) SP2
It seems you wrote a test script that did not cover the full range of possibilities. Include CHAR(198) and CHAR(230) in your test.
(2 row(s) affected)
Doesn't the test sql provided in answer already do that?
On my server it returns 0 rows, so it appears like some other things affect this. Maybe default collation. Probably.
Oh my apologies - I didn't even read the explanation today.
Of course the question should have used a SQL collation, not a Windows one that takes account of Windows language settings. Using a SQL collation would ensure that everyone used the same code page and displayed the same characters (well, almost):
SELECT CHAR(198) COLLATE SQL_Czech_CP1250_CI_AS, CHAR(230) COLLATE SQL_Czech_CP1250_CI_AS;
SELECT CHAR(198) COLLATE SQL_Latin1_General_CP1_CI_AI, CHAR(230) COLLATE SQL_Latin1_General_CP1_CI_AI;
+-------+
¦ A ¦ a ¦
¦---+---¦
¦ Æ ¦ æ ¦
+-------+
December 3, 2012 at 11:15 am
Bex (12/3/2012)
I'll hold my hand up and say I got this right by means of a lucky guess.Very interesting question and excellent, full answer.
Thanks, Tom!
Bex
+1
I wish I could say 'educated'... but it really was 'lucky.'
Thanks, Tom!
December 3, 2012 at 11:37 am
I set up a test script and ran it, and to my surprise got the right answer based on the script outcome.
I was surprised of the results.
Excellent question, Tom!! Keep them coming!
Saludos,
December 3, 2012 at 11:40 am
*blush* Being wrong is teaching me even more about collations.
I'm also seeing another possible advantage to unicode. Switching to unicode, it looks like NCHAR(198) and NCHAR(230) returns the same values (Æ, æ) in Latin and Czech collations. I assume it'll be the same in all collations...
December 3, 2012 at 12:22 pm
I read this question completely different and ended up getting it correct anyway. I guessed two because of '[' and ']'....
I'll take it! 😛
Aigle de Guerre!
December 3, 2012 at 1:46 pm
Excellent Question.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 3, 2012 at 7:22 pm
I've never use Collate and don't know what it does.
I figured the answer would be 5. Like 5 letters excluding the upper case, would leave the 5 lower case.
Not seeing that in the answer, I chose more than 3. Based on some of the comments, I could, technically, be considered correct. 😀
December 4, 2012 at 4:14 am
Thanks. !?
December 4, 2012 at 1:48 pm
Great but difficult question. Thanks Tom.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 15 posts - 16 through 30 (of 38 total)
You must be logged in to reply to this topic. Login to reply