|
|
Posted by Nasir on 10/02/77 11:47
So going back to my original question - seems like it really does not
support at the server level setting of SQL 2005, to achieve table and column
names insensitive and chacter data to be sensitive. Is that correct?
To get the character data sensitive I have to modify each column with
collate, what a mess! I'm surprised that so many people are OK/fine with
Oracle way of dictionary insensitve and data sensitive, but it's so hard to
get thatin SQL. There got to be a btter way!
"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns97C1E7D5DA6Yazorman@127.0.0.1...
> Nasir (nmajeed@prosrm.com) writes:
>> I installed 2005 server with SQL_Latin1_General_CP1_CS_AS in hope to
>> acheive what you described, but look what happens:
>
> David's post may require some clarification.
>
> In SQL Server you can set collation on three levels:
>
> 1) Server
> 2) Database default
> 3) Column level
>
> To simplify, let's assume that server and database default are the
> same.
>
> If you want table names to be case-insensitive (which is a bad idea in
> my opinion), the you install the server with a case-insensitive collation,
> such SQL_Latin1_General_CP1_CI_AS or Latin1_General_CI_AS.
>
> Then you create every table character column to be case-sensitive:
>
> CREATE TABLE t1 (c1 char(10) COLLATE Latin_General_CS_AS NOT NULL)
>
> Obviously, this is quite messy, since you need to specify the collation
> for every column.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|