Am I going mad, since when did T-SQL (2008) become case sensitive?
Stephen.
-
-
Never? It's definitely not on my SQL Server 2008 boxes.
-
Not sure what's happened here, suddenly started getting runtime errors about tables and fields not existing, for example...Sven Groot said:Never? It's definitely not on my SQL Server 2008 boxes.
BAD:
GOOD:
Think it must be something to do with how the database project is deployed, just moved from DBPro GDR CTP16 to CTP17. -
Minor pedant's complaint.PerfectPhase said:
But in the context of security, it's spelled "Principal" not "Principle"
-
I believe this can be specified per-database; it also controls whether 'a' == 'A', for example.
-
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.Matthew van Eerde said:I believe this can be specified per-database; it also controls whether 'a' == 'A', for example.
But maybe PerfectPhase can try to set the server collation to those one of those "CI" types... -
cheong said:
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.Matthew van Eerde said:*snip*
But maybe PerfectPhase can try to set the server collation to those one of those "CI" types...
Good call, it would appear I've built the database with a CS collation rather than CI. Next rebuild I reset it and see what happens.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.