Comments
Sort by recent activity
Turns out the "MyTest" table script only partially replicates the problem. The key is the collation. I also learned that changing the collation on a database doesn't automatically change the collation on the existing tables. So there are two ways to reproduce the issue:
1) Create a database with the default collation set to Latin1_General_100_CI_AI
CREATE DATABASE RedGate1
COLLATE Latin1_General_100_CI_AI
GO
USE RedGate1;
CREATE TABLE MyTest (
[Id] INT PRIMARY KEY IDENTITY(1,1),
[MyValue] TEXT
)
INSERT INTO MyTest (MyValue) VALUES ('some text')
GO
Then create a duplicate database with the same name - the collation on the 2nd database won't matter.
2) OR create a database with the default collation, then create a table whose TEXT column has its collation set to Latin1_General_100_CI_AI
CREATE DATABASE RedGate1
GO
USE RedGate1;
CREATE TABLE MyTest (
[Id] INT PRIMARY KEY IDENTITY(1,1),
[MyValue] TEXT COLLATE Latin1_General_100_CI_AI
)
INSERT INTO MyTest (MyValue) VALUES ('some text')
GO / comments
Turns out the "MyTest" table script only partially replicates the problem. The key is the collation. I also learned that changing the collation on a database doesn't automatically change the collat...