SQLServer2008 is able to see the subscription to Oracle or DB2 when the subscription is being placed, but there is no indirect interface for copying to MySQL.
The end of the test, through MySQL ODBC driver, is able to implement the SQLServer2008 copy to MySQL, thus implementing the schema from the library is SQL Server, read-only library for MySQL.
Firstly, a general distribution and release database is required, not to repeat.
Next, the MySQL ODBC driver is removed and a new system DSN is being created outside the ODBC data flow check-in for replication utilization.
Ftp:anonymous then, you can start creating a new publication for copying to MySQL, and you can create a table for testing.
Once established, the replication environment can be viewed through the replicator. It is also possible to view MySQL database changes from outside SQL Server using the Linkserver mentioned earlier.
The process of testing, has been presented after the point of channeling data, 20203, 20007 and other error numbers, may take the establishment of the release or subscription when the relevant parameters, time is unlimited, there is no specific reason. Oh
There are few places to watch:
1, the establishment of the release replicate_ddl=0, otherwise there will be no error as follows:
Movement 21678, Level 16, pattern 1, Process sp_msrepl_addpublication, line 1110th
The parameter enabled_for_het_sub can be set to true only if REPLICATE_DDL is set to 0 o'clock.
That is, for a homogeneous database, DDL operations can not be replicated, that point later than force trouble.
2, the previously established DSN, for the code outside the Subscriber_datasrc=nmysqltest
3, some of the above parameters do not mean that must be set aside, for reference
4, because, when the test release library is the same instance of the unified Desk server, the result of DSN only set up once, I guess the distribution of the server should be able to set up, currently no more testing.
Http://www.itbcn.cn/article/6307.html
SQL Server 2008 replication to MySQL