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

SQL Anywhere 12.0.1 » UltraLite - Database Management and Reference » UltraLite performance tips » Query performance tips » Execution plans in UltraLite » Determining the access method used by the optimizer » Manage temporary tables


Direct page scans

UltraLite uses direct page scans as an alternative to index scans when it is more efficient to access information directly from the database page. A direct page scan is only used after the optimizer confirms that:

  • No preexisting index can return results more efficiently.

  • You are not using the query to perform updates. For example, you have declared the statement to be FOR READ ONLY (the default setting if no FOR clause has been specified), or have written the query in such a way that it is obvious that data is not being updated.

Because UltraLite reads the rows directly from the pages on which the rows are stored, query results are returned without order. The order of subsequent query results is unpredictable. If you need the order of rows to be predictable and deterministic, use an ORDER BY clause to get results in a consistent order. However, if order is not important, you can omit the ORDER BY clause to improve query performance.


You cannot use direct page scans if you are using a ULTable class in an UltraLite API to program your application.

You can check to see when UltraLite scans a page directly or which index was used to return results.

 See also