Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Collation error on Transactional Replication Expand / Collapse
Author
Message
Posted Thursday, May 8, 2014 4:07 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 4:30 AM
Points: 58, Visits: 297
I am getting an error on a replication subscriber that had previously been working fine. This is the error message:

Command attempted:
if object_id(N'sys.sp_MSrestoresavedforeignkeys', 'P') < 0 exec sys.sp_MSrestoresavedforeignkeys
(Transaction sequence number: 0x0006FC5A0009580901F900000000, Command ID: 1)

Error messages:
Cannot resolve the collation conflict between "Latin1_General_100_CI_AS_KS_WS_SC" and "Latin1_General_CI_AS" in the equal to operation. (Source: MSSQLServer, Error number: 468)
Get help: http://help/468
Cannot resolve the collation conflict between "Latin1_General_100_CI_AS_KS_WS_SC" and "Latin1_General_CI_AS" in the equal to operation. (Source: MSSQLServer, Error number: 468)
Get help: http://help/468
Cannot resolve the collation conflict between "Latin1_General_100_CI_AS_KS_WS_SC" and "Latin1_General_CI_AS" in the equal to operation. (Source: MSSQLServer, Error number: 468)
Get help: http://help/468
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "Latin1_General_100_CI_AS_KS_WS_SC" in the equal to operation. (Source: MSSQLServer, Error number: 468)
Get help: http://help/468

Some details:
It is a push subscription from a SQL Server 2008 R2 publisher to a SQL Server 2012 subscriber that is a member of an AlwaysOn Availability Group.
Two things changed before this error appeared:
- I added a new table to the subscription and marked for re-initialization.
- There was a typo in the subscriber DB name so I dropped the subscription, renamed the database and then recreated the subscription to point at the correct database name.
- There are other tables in the subscription database besides those that are being replicated.

I have verified that both databases are using the same collation and that all columns of replicated tables also have the same collation.
Probably recreating the publication and subscription would fix the issue but I'm reluctant to do this because I don't want to create the snapshot again due to the concurrency issues it creates on the publisher db.
Post #1568810
Posted Thursday, May 8, 2014 4:25 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 9:14 AM
Points: 5,018, Visits: 10,527
Do publisher and subscriber have the same server collation?

--
Gianluca Sartori

Get your two-cent-answer quickly
spaghettidba.com
@spaghettidba
Post #1568816
Posted Thursday, May 8, 2014 5:57 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 4:30 AM
Points: 58, Visits: 297
Yes they do. Both are Latin1_General_CI_AS
Post #1568840
Posted Thursday, May 8, 2014 9:10 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 4:30 AM
Points: 58, Visits: 297
I had to take the nuclear option and recreate the subscription database. Now it is working again.
If anyone has a suggestion as to the original cause however I would be grateful, because I don't want to have to blow away my database if this happens again.
Post #1568962
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse