sql server - Does sqlserver collation mean column names must be correct case? And how to deal with that -


It is possible to set up database or server collaboration in SQL Server (2000 or 2005) so that identifier names (tables, columns, etc.) Should be in the right case? If so, is this true for case-sensitive fusion or is it a different setting? (I have always thought about sensitivity to the case, not applying for the name of the objects, for the data to be applied.)

It may possibly break an application if its stored procs and inquiries consistently Were not written from? To ensure that all questions use the correct position, such as to include the database connection, what is the way to deal without it?

I'm considering the existing application which is probably incompatible with the SQL code in it, and I want to be able to run it against the database with different collations. What settings would I need or how could I not use the database / server collation with the application?

Collation determines what will happen if your question is insensitive. So the only way to ensure that your schema will work against many environments is that the issues of your questions are sensitive. If your questions are not relevant then your fusion case is insensitive or otherwise it will not work.

Can do The case is usually insensitive, and then try to keep your questions continuously.

Once a connection has been set, it applies to both data and metadata, I believe.


Comments