Replication : SQL Server 2000 X MySQL 5.0.41 (Windows)

Good day!

I am carrying through a replication of the transacional and heterogeneous type between the SQL Server 2000 and MySQL 5.0.41, through driver of ODBC of the MySQL (version 3.51.15).

Unhappyly I am not having success!

I make all the necessary configurations, but in the hour to create schema in the MySQL, only the table msrepl7 is created (but nondata) and occurs the following error: “Date too long will be column “timecol” at row 1” and later “Invalid cursor state”.

The first error must to the size of the column timecol that it is created as char (16), but the value that goes to be inserted is to char (19) - > ({ts'2007-05-01 20:45: 21 '}) The table that is published has only two entire fields and the same one is not created in the MySQL, exactly with the option to initiate schema. I looked for in some sites and I found one that said to bind query Log of the MySQL and to catch the command of insert for the table msrelp7 and to insert in the hand, after making this to come back to the SQL Server and to ask for to synchronize again. Did not function, now only with the error of “Invalid cursor state”! To complete one another person in one another site it placed that was to exclude the table msrepl7 that everything would function, did not function!

Thanks!!

Cristiano Rodrigues

you'll have to search this forum and/or the web for help with MySQL subscribers, Microsoft currently provides supports for SQL Server, Oracle and DB2 subscribers.

Replication - duplicate key

I am activating a replication of the transacional type with only one table.
Everything enable normal, at the moment to pass the data appears the
following message:
String data, right truncation
(Source: 172.18.7.22 (ODBC); Error number: 22001)
------
Unexpected EOF encountered in BCP data-file
(Source: 172.18.7.22 (ODBC); Error number: S1000)
------
Violation of PRIMARY KEY constraint 'PK__PDVMAP__55AB7606'. Cannot insert
duplicate key in object 'PDVMAP'.
(Source: 172.18.7.22 (Data source); Error number: 2627)
However in the destination it does not have these data, not have duplicate
key, as much that I obtain to export the same data for the DTS.
Do you get this error if you use character mode format?
Are you replicating to a table and dropping it before you recreate it?
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Carla" <Carla@.discussions.microsoft.com> wrote in message
news:B9386AF0-7D2C-4A50-A240-8BE70C1A2F0D@.microsoft.com...
> I am activating a replication of the transacional type with only one
table.
> Everything enable normal, at the moment to pass the data appears the
> following message:
> String data, right truncation
> (Source: 172.18.7.22 (ODBC); Error number: 22001)
> ----
--
> Unexpected EOF encountered in BCP data-file
> (Source: 172.18.7.22 (ODBC); Error number: S1000)
> ----
--
> Violation of PRIMARY KEY constraint 'PK__PDVMAP__55AB7606'. Cannot insert
> duplicate key in object 'PDVMAP'.
> (Source: 172.18.7.22 (Data source); Error number: 2627)
> However in the destination it does not have these data, not have duplicate
> key, as much that I obtain to export the same data for the DTS.
|||i′m using this configurates:
in the table article propertier - snapshot - if a table named xx exist at
the subscriber: keep the existing table unchanged.
Copy objects to destination:
It′s marked the options:
Include declared referential integrity
Clustered indexes
Nonclustered indexes
User triggers
extended properties
[]′s
"Hilary Cotter" wrote:

> Do you get this error if you use character mode format?
> Are you replicating to a table and dropping it before you recreate it?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
>
> "Carla" <Carla@.discussions.microsoft.com> wrote in message
> news:B9386AF0-7D2C-4A50-A240-8BE70C1A2F0D@.microsoft.com...
> table.
> --
> --
>
>