SQL Case sensitivity | Tech Off

PerfectPhase
"This is not war, this is pest control!" - Dalek to Cyberman

Am I going mad, since when did T-SQL (2008) become case sensitive?

Stephen.

Sven Groot
My name has 9 letters. Coincidence? I think not...

Never? It's definitely not on my SQL Server 2008 boxes.

PerfectPhase
"This is not war, this is pest control!" - Dalek to Cyberman

In reply to Sven Groot

#Oct 2nd, 2008 @ 9:57 AM

Not sure what's happened here, suddenly started getting runtime errors about tables and fields not existing, for example...

BAD:

GOOD:

Think it must be something to do with how the database project is deployed, just moved from DBPro GDR CTP16 to CTP17.

W3bbo
The Master of Baiters

In reply to PerfectPhase

#Oct 2nd, 2008 @ 10:31 AM

Minor pedant's complaint.

But in the context of security, it's spelled "Principal" not "Principle" Smiley

Matthew van Eerde
AKA Maurits

I believe this can be specified per-database; it also controls whether 'a' == 'A', for example.

cheong

In reply to Matthew van Eerde

#Oct 2nd, 2008 @ 2:40 PM

Setting to collation to "CS"s instead of "CI"s of database will definately affect your case, but I doubt that'll affect how the server interprete the SQL statements as well.

But maybe PerfectPhase can try to set the server collation to those one of those "CI" types...