SQL Server2000+sql Server Mobile Edition configuration merge replication

The configuration of merge replication is being studied recently. The environment I need is this, the server-side database is SQL Server 2000.PPC, and the thin database The client uses is SQL Server Mobile Edition.

The most commonly used database alignment is SQL Server 2005 and SQL Server Mobile Edition. In fact, I would like to adopt this. However, considering the original database system is a version of 2000, it is difficult to let the original developers to spend time to complete the migration.

Originally, the Streamlined database to choose SQL CE 2.0. However, the installation prerequisite conditions of the server tool will never be successfully resolved during the installation process. (Probably, with the VS2005 or Sql2005 I've installed, I haven't had time to test the installation environment without Vs2005 and Sql2005 interference.) ）

If you are working with MSsql2000 for merge replication, you must install SQL Server Mobile Edition before installing the SP3 for MSSQL 2000 and SP3 for SqlCe. Only two patches are installed, and SQLCE 3.0 installs the program to detect that SQL 2000 already has a replication component.

When this step is over, create the snapshot folder, create the publication, set access rights, security parameters, Web Synchronization Wizard configuration, and final programming tests. You can refer to this article in MSDN. Although this article is for version 2005, the terms and concepts mentioned in it are found in SQL Server 2000. So step by step is OK.

The last thing to note is that the steps of the subscription can be omitted. You cannot configure a subscription that conforms to SQL CE in SQL Server 2000. (At least I think it's not configurable). The only way to test if you can implement merge replication is by programming. That is, programmatically adding a subscription, and then implementing synchronization.

When testing a use case program, we may encounter exceptions. Catches an exception message, which, if it is a reminder that the snapshot message is obsolete, requires a rebuild of the snapshot. The problem is that there is a problem with the dispatch settings of the agent program. Perhaps this snapshot has not yet been generated, in other words, the agent has not been scheduled. To solve it, that is to modify the parameters of the schedule. In order to best set the schedule directly to 1min/times.

This completes the configuration. It worked. Synchronization is also in normal.

Please contact the site, timely note your name. Contact Email: edu#chinaz.com (change # to @).