Collation Conflict with Snapshot Rep

I'm trying to setup replication from an external web server to internal sql
box. The internal box with do a pull subscription to external webbox. I ran
snapshot and all works successfully. As soon as I try to run Pull
subscription, I get an error a Collation Conflict on a table. I tweaked the
settings and copy the collation to destination in the publication properties
tab. This runs but gives me the following:
Error Message: Cannot resolve collation conflict for equal to operation.
Error Detail: Cannot resolve collation conflict for equal to operation.
(Source: WIN2K3 (Data source); Error number: 446)
ANy ideas on how to correct this?
Thanks in Advance
Rob
Is there anything odd about the particular table you are having a problem
with? Could you post its schema here? What sort of content is inside this
table?
Also it sounds like you are doing filtering. Are you?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:18B8B552-CC29-4F84-B073-34FF3FF6BBED@.microsoft.com...
> I'm trying to setup replication from an external web server to internal
> sql
> box. The internal box with do a pull subscription to external webbox. I
> ran
> snapshot and all works successfully. As soon as I try to run Pull
> subscription, I get an error a Collation Conflict on a table. I tweaked
> the
> settings and copy the collation to destination in the publication
> properties
> tab. This runs but gives me the following:
> Error Message: Cannot resolve collation conflict for equal to operation.
> Error Detail: Cannot resolve collation conflict for equal to operation.
> (Source: WIN2K3 (Data source); Error number: 446)
> ANy ideas on how to correct this?
> Thanks in Advance
> Rob
>
|||No filtering, straight snapshot. Nothing odd about the table or its data.
Its a third
party program so I cannot change the table structure.
Heres the table setup.
CREATE TABLE [TABLE1] (
[nm_entity] [varchar] (30) COLLATE Latin1_General_BIN NOT NULL ,
[no_next_internal_id] [int] NOT NULL ,
[no_next_parameter_id] [int] NULL ,
[no_next_code_suffix] [int] NULL ,
CONSTRAINT [Table1_PK] PRIMARY KEY CLUSTERED
(
[nm_entity]
) WITH FILLFACTOR = 90 ON [PRIMARY]
) ON [PRIMARY]
When SQL creates snapshot this is the table structure on the
pull subscriber:
CREATE TABLE [THINQ_ID_MANAGER] (
[nm_entity] [varchar] (30) COLLATE Latin1_General_BIN NOT NULL ,
[no_next_internal_id] [int] NOT NULL ,
[no_next_parameter_id] [int] NULL ,
[no_next_code_suffix] [int] NULL
) ON [PRIMARY]
GO
thanks
rob
"Hilary Cotter" wrote:

> Is there anything odd about the particular table you are having a problem
> with? Could you post its schema here? What sort of content is inside this
> table?
> Also it sounds like you are doing filtering. Are you?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Rob" <Rob@.discussions.microsoft.com> wrote in message
> news:18B8B552-CC29-4F84-B073-34FF3FF6BBED@.microsoft.com...
>
>
|||What is the default collation sequence on your publisher and the default
collation sequence on your subscriber?
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:4B47392D-0477-4842-9173-762D00AE5267@.microsoft.com...[vbcol=seagreen]
> No filtering, straight snapshot. Nothing odd about the table or its
> data.
> Its a third
> party program so I cannot change the table structure.
> Heres the table setup.
> CREATE TABLE [TABLE1] (
> [nm_entity] [varchar] (30) COLLATE Latin1_General_BIN NOT NULL ,
> [no_next_internal_id] [int] NOT NULL ,
> [no_next_parameter_id] [int] NULL ,
> [no_next_code_suffix] [int] NULL ,
> CONSTRAINT [Table1_PK] PRIMARY KEY CLUSTERED
> (
> [nm_entity]
> ) WITH FILLFACTOR = 90 ON [PRIMARY]
> ) ON [PRIMARY]
> When SQL creates snapshot this is the table structure on the
> pull subscriber:
> CREATE TABLE [THINQ_ID_MANAGER] (
> [nm_entity] [varchar] (30) COLLATE Latin1_General_BIN NOT NULL ,
> [no_next_internal_id] [int] NOT NULL ,
> [no_next_parameter_id] [int] NULL ,
> [no_next_code_suffix] [int] NULL
> ) ON [PRIMARY]
> GO
> thanks
> rob
>
>
> "Hilary Cotter" wrote: