New platforms and devices   Windows Vista is now supported in this release.

Improved SQL performance   Historically, UltraLite would default to using the primary key index if, the UltraLite query optimizer determined that there was not any benefit to using an existing index for the query.

With this version, instead of using the primary key, UltraLite will now access rows directly from the database pages. When this happens, you can expect to see query results returned in a different order from previous releases, because rows are no longer ordered by the primary key index. If the ordering of data is a concern, use an ORDER BY clause in your query. See Using direct page scans and Using index scans.

Database property and option accessibility via SQL   Previous versions only allowed you to access database properties and options with methods from each UltraLite API. Now, UltraLite SQL introduces the following statement and function, so that you can set and retrieve properties and options via SQL (including Interactive SQL):

Increased number of concurrent connections   UltraLite now supports more concurrent connections. A single database still supports 14 connections. However, the number of overall concurrent database connections have increased:

Commit flush operations   Historically, any commit operation performed with either the COMMIT statement or API call would only complete after UltraLite flushed a transaction safely to storage. With this release, you can now configure these behaviors and logically separate them as distinct operations:

However, you can also enhance the performance of UltraLite applications that use the autocommit feature—particularly if you use group commit flushes. See Backing up and recovering data in UltraLite and Flushing single or grouped transactions.

This new behavior is supported with the following features: