Re: Error in Inintial Replication

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Mark Allison (marka_at_no.tinned.meat.mvps.org)
Date: 09/28/04 

Date: Tue, 28 Sep 2004 12:11:43 +0100

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: Installing SQL_Latin1_General_CP1_CI_AS collation order??
    ... collations, where a collation controls things as the character repertoire, ... Tibor Karaszi, SQL Server MVP ... "Ward Horsfall" wrote in message ...
    (microsoft.public.sqlserver.setup)
  • Re: Replication Monitor didnt work because different collations
    ... Looking for a SQL Server replication book? ... SQL 2005 filtered merge replication. ... We changed collations to match the server collation and Replication ... After this change we started all publication snapshots. ...
    (microsoft.public.sqlserver.replication)
  • RE: Collation....
    ... ANSI SQL-92 suggests that two strings which differ only in trailing spaces ... In SQL Server, with most collations a simple ...
    (microsoft.public.sqlserver.programming)
  • Re: sort order ID
    ... SQL Server allows to create different collations for each database inside ... Get the equalent collations in SQL 2000 from books online. ... > 52 collations differece from server. ...
    (microsoft.public.sqlserver.server)