Version: 14.0-dev-37

Build #: 31885

Build Date: 2013-Apr-10 08:20:37 AM

 

Collation is scripted for table columns even when it has same database default collation

To reproduce:

 

1. Connect to Windows Azure and SQL Server and create the below table

 

CREATE TABLE [dbo].[Col_Sample]  ( 

        [a1]    varchar(25) NOT NULL,

        [a2]    varchar(25) NOT NULL,

        [a3]    varchar(25) NOT NULL,

        [a4]    varchar(25) NOT NULL,

        [a5]    varchar(25) NOT NULL 

        )

2. Do a Script to Window->Full in both Azure and SQL Server.

3. You can see that Azure scripts the table with Collation, where as SQL Server doesnt

4. If you do a Schema Compare and select the table created in Azure and SQL Server, changes will be displayed due to the difference in collation

 

See attached pic

 

From Nhi: 

In Sql Server, it has special code to set collation = null when it's the same as the database default collation, and azure code doesn't do that.

 

Bug reported by Rohit Rana