Re: Error in Inintial Replication

From: Jeff Dillon (jeff_at_removeemergencyreporting.com)
Date: 09/28/04


Date: Tue, 28 Sep 2004 08:09:10 -0700

As I stated, they do have the same collation. Even using an empty database
as the subscriber causes this. So far, it appears the tables that are
failing have text columns.

I did a Google search on this, and the common reply is to check collation.
In neither of the 2 cases I found was collation the issue. It was never
resolved. Appears to be a bug.

I run sp_helpsort in each database, and it returns the same results. Is
there somewhere else I need to check?

Jeff

"Mark Allison" <marka@no.tinned.meat.mvps.org> wrote in message
news:O8JpwvUpEHA.2948@TK2MSFTNGP11.phx.gbl...
> Jeff,
>
> Make sure the publisher and subscriber have the same collations - this
> is normally due to differing collations.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
>
> Jeff Dillon wrote:
> > I'm Replicating from one SQL200 db to another on our LAN. The target db
is
> > blank, but on some of the tables, it fails with:
> >
> > Could not bulk insert. Bulk data stream was incorrectly specified as
sorted.
> > (Source: STAN (Data source); Error number: 4819)
> >
> > I've verified that the collation and sort order are the same. Any ideas?
> >
> > Jeff
> >
> >



Relevant Pages

  • Re: Error in Inintial Replication
    ... Jeff ... > I did a Google search on this, and the common reply is to check collation. ... Appears to be a bug. ... >> Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.server)
  • Re: Error when making a transactional replication
    ... The publication database had a different collation than the subscriber. ... Bulk data stream was incorrectly specified as ...
    (microsoft.public.sqlserver.replication)
  • Re: Case Sensitive
    ... on the publisher is case-sensitive and this has replicated to the subscriber ... as a case-insensitive collation. ... need to reinitialize for this to take effect. ...
    (microsoft.public.sqlserver.server)
  • Re: Case Sensitive
    ... on the publisher is case-sensitive and this has replicated to the subscriber ... as a case-insensitive collation. ... need to reinitialize for this to take effect. ...
    (microsoft.public.sqlserver.programming)
  • Re: Case Sensitive
    ... on the publisher is case-sensitive and this has replicated to the subscriber ... as a case-insensitive collation. ... need to reinitialize for this to take effect. ...
    (microsoft.public.sqlserver.replication)