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

SQL Anywhere 10.0.1 » UltraLite - Database Management and Reference » Creating and Configuring UltraLite Databases » Choosing creation-time database properties for UltraLite

UltraLite page size considerations Next Page

UltraLite security considerations

By default, UltraLite databases are unencrypted on disk. Text and binary columns are plainly readable within the database when using a viewing tool such as a hex editor. If you need to encrypt data for greater security, consider the options listed below.


The MobiLink server's synchronization streams can use public/private keys to encrypt streamed data. For ease of deployment, you can embed these certificates in the UltraLite database when you create it. See Configuring MobiLink clients to use transport-layer security.


Both the FIPS and AES database encryption types use 128-bit AES. This means that if you use the same encryption key, the database is encrypted the same way irrespective of the standard you choose.


You can change the encryption key after the database has been created, but only under extreme caution. See:

This operation is costly and is non-recoverable: if your operation terminates mid-course, you will lose your database entirely.

Additionally, if you lose or forget the encryption key for a strongly encrypted database, there is no way to access the data in it—even with the assistance of technical support. The database must be discarded and you must create a new database.

See also

Setting up an AES FIPS database encryption in UltraLite