ALTER TABLE SWITCH statement failed because column '%.*ls' does not have the same collation in tables '%.*ls' and '%.*ls'.

Error Message:
Msg 4945, Level 16, State 1, Line 2
ALTER TABLE SWITCH statement failed because column ‘%.*ls’ does not have the same collation in tables ‘%.*ls’ and ‘%.*ls’.

Severity level:
16.

Description:
This error message appears when you try to run an ALTER TABLE SWITCH statement for which columns in the base tables do not have the same collation.

Consequences:
The T-SQL statement can be parsed, but causes the error at runtime.

Resolution:
Errors of the Severity Level 16 are generated by the user and can be fixed by the SQL Server user. The statement cannot be executed this way. Columns in the participating tables must have the same collation.

Versions:
This error message was introduced with SQL Server 2005.

Example(s):
USE tempdb;
GO
SET NUMERIC_ROUNDABORT OFF;
SET ANSI_PADDING,
    ANSI_WARNINGS,
    CONCAT_NULL_YIELDS_NULL,
    ARITHABORT,
    QUOTED_IDENTIFIER,
    ANSI_NULLS ON;
GO

CREATE PARTITION FUNCTION myPartFunction (int)
    AS RANGE LEFT FOR VALUES (1, 10, 100);
GO

CREATE PARTITION SCHEME myPartScheme
    AS PARTITION myPartFunction
   ALL TO ([PRIMARY]);
GO

CREATE TABLE myPartTable
(
 c1 int,
 c2 varchar(10) COLLATE Albanian_BIN
)
ON myPartScheme (c1);

GO
CREATE TABLE myNonPartTable
(
 c1 int,
 c2 varchar(10) COLLATE Arabic_BIN
)
ON [PRIMARY];
GO

ALTER TABLE myPartTable SWITCH PARTITION 1 TO dbo.myNonPartTable ;
GO

DROP TABLE myNonPartTable, myPartTable;
DROP PARTITION SCHEME myPartScheme;
DROP PARTITION FUNCTION myPartFunction;

Remarks:
In the above example we try to run an ALTER TABLE SWITCH statement. Because the column c2 does not have the same collation in the participating tables, the error is raised.

]]>

Leave a comment

Your email address will not be published.