Forever I’ve used a case sensitive collation in Sql Server (SQL_Latin1_General_CP1_CS_AS). I’m trying to move to Sql Azure Database and I’ve run into an unexpected problem. It looks like it’s impossible to have case sensitive column names. Can this be true?
I create my database…
CREATE DATABASE MyDatabase COLLATE SQL_Latin1_General_CP1_CS_AS
And I create my table…
CREATE TABLE [MyTable] ( [Name] NVarChar (4000) COLLATE SQL_Latin1_General_CP1_CS_AS NULL, [name] NVarChar (4000) COLLATE SQL_Latin1_General_CP1_CS_AS NULL )
And I get the error: Column names in each table must be unique. Column name ‘name’ in table ‘MyTable’ is specified more than once.
Ugh, disaster. This works perfectly in Sql Server 2012. However on Sql Azure I can’t seem to make it happen. Does anyone know why this is not working in Sql Azure? Does anyone know how I can make this work in Sql Azure? Thanks.
I think this is a bug in Windows Azure SQL!
On line documentation states that you can override the collation at the database, column or expression levels. You can not do it at the server level.
Lets start with something we know will work, a local install of SQL Server 2012.
-- Start at master Use master; Go -- Create a new database CREATE DATABASE Koopa COLLATE SQL_Latin1_General_CP1_CS_AS; -- Use the new database Use Koopa; Go -- Create a new table CREATE TABLE [MyTable] ( [ColName1] NVarChar (4000) COLLATE SQL_Latin1_General_CP1_CS_AS NULL, [colname1] NVarChar (4000) COLLATE SQL_Latin1_General_CP1_CS_AS NULL );
If we try to run the create table in the MASTER database, we get your error.
Msg 2705, Level 16, State 3, Line 2
Column names in each table must be unique. Column name ‘colname1’ in table ‘MyTable’ is specified more than once.
If we run the create table in the Koopa database, it works fine. See image below. That is because MASTER is Case Insensitive CI!
I am going to use the Web Interface for Azure SQL database since it has nice colors (it is the web)!
Let’s create a new database with the Case Sensitive collation. Wow I am getting excited since there is an option to select our collation.
Now that we have a new database, lets check the settings!
I am still happy since we see the correct collation listed for the database.
Lets log onto the database server directly and run a simple query to create the table.
I am going to try the designer first!
Oops, It did not work.
Lets try a simple DDL statement in a query window.
Now I am really disappointed. We were sold a bill of goods but Azure SQL did not deliver.
In short, the documentation says you can not set the collation at the server level.
However, this Quote from BOL states we should be able to over ride it at the database level.
Server-level collations The default server collation is set during SQL Server setup, and also becomes the default collation of the system databases and all user databases. Note that Unicode-only collations cannot be selected during SQL Server setup because they are not supported as server-level collations.
In short, I am extremely busy with a couple speaking engagements for PASS the next 7 days. I will have to open a bug report or see if there is one already open.
BTW – You now need to use distinct column names.