Upgrading to SQL Server Mobile
Server Tools and Service Pack Levels
You can connect SQL Server 2005 Mobile Edition to SQL Server 2000 SP3a and later versions. Similarly, you can connect SQL Server CE 2.0 to SQL Server 2005. Setup instructions and the SQL Server Mobile components are available on the Connectivity Tools page.
SQL Server users and developers upgrading to SQL Server Mobile must ensure their SQL Server Mobile server-side components have the same service pack installed as they have on SQL Server 2000. Whether you installed your SQL Server CE Server Tools on the computer running Microsoft Internet Information Services (IIS) and SQL Server or you installed it on a separate computer, you will need to update your server tools to work with the Service Pack on your database.
Note: The SQL Server Mobile Server Tools are not a replacement for SQL Server 2000 Service Packs. The server tools are updates to the replication and data access components relevant to SQL Server CE. Visit the SQL Server Downloads page to download the most recent service pack for SQL Server.
Coexistence with Previous Versions
SQL Server Mobile maintains two versions of the product side by side. The two versions of SQL Server Mobile can coexist on the same computer. This enables a simple and gradual upgrade process. SQL Server Mobile connectivity requires that the client components on the supported devices and the server components installed on the computer that is running IIS be the same major-release version.
Upgrading Database Files
You can upgrade a database created with an earlier version of SQL Server CE 2.0 to a database created with SQL Server Mobile by using the SQL Server Mobile Database Upgrade tool (upgrade.exe). The Database Upgrade tool runs on a smart device.
When you run the SQL Server Mobile Database Upgrade tool, the new SQL Server Mobile database is created on the smart device. The new database, with the file name extension .sdf, contains all the data that was in the source database. You need to reinitialize the upgraded database to continue using it for replication.
Note: If you are using replication or remote data access (RDA) as a connectivity solution before upgrading to SQL Server Mobile, you must synchronize the source SQL Server CE database (subscription database) with the SQL Server database (Publisher). The reason for synchronizing before upgrading to SQL Server Mobile is to ensure that any changes that exist in the tables on the SQL Server CE database are updated on the SQL Server database, because after the upgrade you must resubscribe or repull using the new database.
Upgrading Distributed Applications
When you upgrade, first install SQL Server Mobile Server Tools, and then install the client components. Do not deploy newer client applications if you still have an earlier version of SQL Server CE Server Tools on the computer that is running IIS. After all components are in place, redeploy the application to your smart devices.
During the application upgrade process, you must change any references of SQL Server CE version 1.0, SQL Server CE version 1.1, and SQL Server CE version 2.0 to SQL Server Mobile. When you upgrade the computer that is running IIS, you must install SQL Server Mobile Server Tools. You can then configure a new virtual directory for SQL Server Mobile clients on this computer. As you deploy SQL Server Mobile client components to your devices, you must update your application to use this new virtual directory for SQL Server Mobile by updating the InternetURL property of your replication or RDA objects. The new InternetURL property points to sqlcesa30.dll instead of Sscesa10.dll or Sscesa20.dll. Updating the InternetURL property is critical because the SQL Server Mobile Client Agent can communicate only with the SQL Server Mobile Server Agent.
Note: Ensure that the upgraded application is available and functioning correctly before you remove the previous release of your application and the SQL Server CE client components.