1
Vote

3.7.7 Introduces Bug w/ Non Default Collation

description

We have SQL_Latin1_General_CP1_CS_AS collation on one of our tables that seems to be ignored during migration.
 
The subsequent BCP insertions then trigger errors as they're in violation of the unique constraints.
 
This seems to be unique to the 3.7.7 release as it didn't exist in the version before.

comments

ghuey wrote Oct 6, 2011 at 2:57 PM

Hi,

Is this problem now on all tables or just one of your tables? If just one table, would you be willing to share the table schema with me so I can look? You can contact me offline (via codeplex).

Thanks,
George