|
|
|
|
|
|
|
|
|
|
- Overview
- How to?
- Optimizing the execution speed of current query
- Optimizing the execution speed of one or more queries
- Optimization and composite keys
Optimizing the query execution
 Warning
From version 23, this feature is only available via the HFSQL Control Center notification system. For more details, see Notifications of an HFSQL server.
The query editor allows you to optimize the execution speed of one or more queries. The optimization of a query is based on the following principle: a wizard defines the composite keys to modify and/or to add into the analysis associated with the project. Optimizing the execution speed of current query To optimize the execution speed of current query: - On the "Query" tab, in the "Analyze" group, click "Optimize the query".
- The window for query optimization is displayed and it proposes the different modifications that can be performed in the analysis.
Optimizing the execution speed of one or more queries To optimize the execution speed of one or more queries: - On the "Query" tab, in the "Analyze" group, click "Optimize the query".
- The window for query optimization is displayed and it proposes the different modifications that can be performed in the analysis.
Caution: Adding a large number of composite keys to the analysis increases the index file size and may slow down the access to data files. Remark: This option is available only if the following conditions are fulfilled: - the Live Data is enabled: on the "Project" tab, in the "Project" group, click "Description". Select the "Live Data" tab and check "Enable the Live Data". For more details, see Live Data.
- the data files are found in the test directory of project: on the "Project" tab, in the "Project" group, click "Description". Select the "Files" tab. For more details, see Testing a project.
Optimization and composite keys To optimize your queries, the editor proposes the creation of composite keys. The order of components in the composite key is not important. There is no need to create a new key that just reverses the order of components found in an existing key.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|