SQL Server 2005 to SQL CE 2.0

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

jc.sparky@gmail.com - 05 Dec 2007 14:50 GMT

I have merge replication configured between SQL Server 2000 and SQL CE
2.0 which has been working fine for the past few years. I need to
migrate my Server 2000 database to SQL Server 2005 and set up merge
replication there. Can I simply point my device to the new database
on SQL Server 2005 and have merge replication working using SQL CE 2.0
without making any changes on the device (i.e. upgrading to a newer
version of SQL CE)?

Reply to this Message

jc.sparky@gmail.com - 05 Dec 2007 21:09 GMT

... to add more information, I'm syncing with the server and
downloading the updates just fine but I get the following error when
the updates are applied to the device db....

Error:80004005
Run
Native Error:28557
Microsoft SQL Server 2000 Windows CE Edition
E-Parm:data source=\Storage Card\Feline\Feline Data
\DBFeline.sdf;ssce:temp file directory=\Temp\;
Error:80040E14

Native Error:28560
Microsoft SQL Server 2000 Windows CE Edition
Error:80040E14

Native Error:25501
Microsoft SQL Server 2000 Windows CE Edition
N-Parm:1
N-Parm:1
E-Parm:SET

Reply to this Message

ErikEJ - 06 Dec 2007 10:13 GMT

According to this page:
http://www.microsoft.com/sql/editions/sqlmobile/connectivity-tools.mspx
your scenario is supported. The 28557 error indicates that you have another
open connection to your database (that should be closed).

Signature

Erik Ejlskov Jensen - MCTS: Mobile App Dev

> .... to add more information, I'm syncing with the server and
> downloading the updates just fine but I get the following error when
[quoted text clipped - 17 lines]
> N-Parm:1
> E-Parm:SET

Reply to this Message

jc.sparky@gmail.com - 07 Dec 2007 15:11 GMT

I am running the same code that I used in the SQL Server 2000 to SQL
CE 2.0 that worked just fine. All I changed was the location of the
database from a SQL Server 2000 server to a SQL Server 2005 server.

Reply to this Message

jc.sparky@gmail.com - 12 Dec 2007 22:38 GMT

Issue solved. I needed to upgrade my server components to SQL Server
2000 SP4 components.

Reply to this Message