Installing the Microsoft SQL Server 2005 Mobile Edition Device SDK
Microsoft SQL Server 2005 Mobile Edition (SQL Server Mobile) Device SDK is used for installing SQL Server Mobile on mobile devices, and for developing applications based on mobile devices.
Before installing SQL Server 2005 Mobile Edition Device SDK, you must complete the following steps:
1. | Review the SQL Server 2005 Mobile Edition System Requirements. |
2. | Ensure that you have Microsoft ActiveSync 4.0 or later. |
3. | Verify that you have Administrator rights on the target system and that the Administrators group has Change permission on the installation directory. |
4. | Download the SQL Server 2005 Mobile Edition Device SDK and install it in a directory (the default is Microsoft SQL Server 2005 Mobile Edition). The .cab files for installing SQL Server Mobile on the devices are installed on the hard drive in per the following structure. Select the operating system and the processor type to install SQL Server Mobile on the mobile device. The .cab files for installing the SQL Server Mobile on the mobile device are under the directory "Mobile" and the components for directly connecting to SQL Server from the mobile device are under the folder "Client."
-> Microsoft SQL Server 2005 Mobile Edition (CONFIGURABLE)
-> Docs
-> SQL Server Mobile 2005.chm
-> ssmreadme.htm
-> Device
-> EULA.rtf
-> Mobile
-> v3.0
-> wce400
-> Sub Directories: armv4
-> wce500
-> Sub Directories: armv4i, mipsii, mipsii_fp, mipsiv, mipsiv_fp, sh4, i486
->Tablet PC
-> Client
-> v2.0
-> wce400
-> Sub Directories: armv4
-> wce500
-> Sub Directories: armv4i, mipsii, mipsii_fp, mipsiv, mipsiv_fp, sh4, i486
|
5. | The DLLs and the Headers required for developing a SQL Server Mobile application are also made available with the SQL Server 2005 Mobile Edition Device SDK download. The details are as follows: Managed: System.Data.SqlServerCe.dll System.Data.SqlClient.dll Native: ca_merge30.h – Connectivity ssceerr30.h – Errors ssceoledb30.h – OLE DB Provider Interfaces Except for SqlClient.dll, all others go in the DeviceSdk\Mobile\v3.0 directory. SqlClient.dll is placed under the DeviceSdk\Client\v2.0 directory. Refer to the preceding directory structure. |
Note: SQL Server Mobile contains three .cab files: sqlce30.[platform].[processor].cab, sqlce30.repl.[platform].[processor].cab, and sqlce30.dev.[platform].[processor].cab. The following table describes the DLLs that make up these three .cab files. It also explains the scenarios in which you need the specific .cab files.
| sqlce30.[platform].[processor].cab | sqlce30.repl.[platform].[processor].cab | sqlce30.dev.[platform].[processor].cab | ||||||||||||||||||||
Contains the following DLLs:
If you want to create a SQL Server Mobile application using only the Storage Engine and query processor capabilities, you need all of these DLLs. You can either package the DLLs installed under C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\Device\Mobile\v3.0\platform\processor in your own setup or install this .cab file on your device. | Contains the following DLLs:
If you want to use merge replication or remote data access (RDA), then, in addition to the DLLs packaged with sqlce30.[platform].[processor].cab, you need these three DLLs. You can either package the DLLs shipped in the SDK directory, or you can install this .cab file. | Contains the following files:
If you are developing and testing an application, install this .cab file, which includes the SQL Server Mobile error messages and query analyzer. |
Apart from the preceding three SQL Server Mobile .cab files, two other .cab files provide the System.Data.SqlClient namespace functionality. SQL Client is used for connecting to SQL Server directly from the device without involving the SQL Server Mobile database. The two .cab files are sql.[platform].[processor].cab and sql.dev.[platform].[processor].cab.
For More Information:
Read the End User License Agreement for SQL Server Mobile.
