Matching sqlserver means that the column names must be correct. And how to deal with it

Question

In SQL Server (2000 or 2005), can you map a database or server so that the identifier names (tables, columns, etc.) are in the right case? If so, is this true for all case sensitive sorts or is it a separate setting? (I always thought about case sensitivity applied to data, not object names).

Presumably this will break the application if its saved procs and requests were not written with a sequential case? Is there a way to handle this without requiring that all queries use the correct case, for example, by setting up a database connection mapping?

I am considering this from the point of view of having an existing application that probably has unique SQL code in it, and I want to be able to run it with databases with different mappings. What parameters do I need or what set of database and server mappings can I not use the application?

Answer 1

- , , . , , , - . , , .

http://msdn.microsoft.com/en-us/library/aa174903(SQL.80).aspx

, , SQL Server , , NEW SQL Server. , - , , . .

, . .

Answer 2

SQL Server ​​, 2005 , .

Answer 3

, - : , ..

, , ( , -proc, , SQL).

, , , , , (, GROUP BY -).

Answer 4

.

How to deal with it? You need to enforce standards here. You can easily get confused when different people write in another case.

Comparison also applies to data, so "bob"! = "Bob"