Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.1 » SQL Anywhere Server - Database Administration » Starting and Connecting to Your Database » SQL Anywhere for Windows Mobile


Configuring Windows Mobile databases

Most SQL features available in the full version of SQL Anywhere are also available in the Windows Mobile version. These include transaction processing, referential integrity actions, procedures and triggers, and so on. However, the Java features and the remote data access features are not available on Windows Mobile.

You should be mindful of the unsupported features when setting database properties on a database intended for a Windows Mobile device.

For a complete list of unsupported features, see SQL Anywhere feature support on Windows Mobile.

The following settings are configured during database creation. Once set, these properties can only be changed by rebuilding the database.

  • Case sensitivity or insensitivity   See Case sensitivity.

  • Treatment of trailing blanks in comparisons   By default, databases are created with trailing blanks classified as extra characters. For example, 'Dirk' is not the same as 'Dirk '. You can create databases with blank padding, so that trailing blanks are ignored. See Ignore trailing blanks in comparisons.

  • Page size   See Table and page sizes.

  • Collation sequence and character set   When creating databases for Windows Mobile, you should use a collation based on the same single- or multibyte character set that Windows would use for the language of interest. For example, if you are using English, French, or German, use the 1252Latin1 collation. If you are using Japanese, use the 932JPN collation, and if you are using Korean, use the 949KOR collation. See Understanding collations.


    Do not specify a locale or a sorttype in the tailoring options string when creating a database for use on Windows Mobile. If you do, it is likely that the will not start on the Windows Mobile device. For more information about collation tailoring options, see Collation tailoring options.

    Because character set translation is not supported on Windows Mobile, you must use either the operating system character set or UTF-8 for Windows Mobile databases.

    You must choose whether you want to install the ICU library when creating your Windows Mobile database. See Installation considerations: Using ICU on Windows Mobile.

Using a transaction log on Windows Mobile
Using jConnect on Windows Mobile
Using encryption on Windows Mobile
Creating a Windows Mobile database
Rebuilding databases on Windows Mobile
Backing up a Windows Mobile database
Erase a Windows Mobile database