|
|
Posted by Erland Sommarskog on 10/02/41 11:47
Nasir (nmajeed@prosrm.com) writes:
> 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!
Yes, if you try to use SQL Server as if it was Oracle, or vice versa, it
will be very painful.
I can agree that Oracle's way has a point - but in such case I would use
it the other way round: data case-insensitive, metadata case-sensitive.
My strong recommendation is that for development you should use case-
sensitive collation. Because if you develop under case-insensitive, and
the customer insists on case-sensitive, and you have used case
inconsistently, it will be very difficult to sort out. A collorary is that
it's a good idea to stick with all lowercase for names, so you don't end up
with both t1 and T1.
--
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]
|