|
|
|
|
|
|
|
|
|
|
- Differences between HOptimize and HOptimizeQuery
- Miscellaneous
<Source>.Optimize (Function) In french: <Source>.Optimise
 Available only with this kind of connection
Allows you to handle the idle periods of a software (period without processes) to optimize the queries and the browses that will be run thereafter. Optimizes the access to the indexes of HFSQL Classic data files (the indexes of HFSQL Client/Server data files cannot be optimized). Syntax
<Result> = <Source>.Optimize([<Key item>])
<Result>: Boolean - True if the file was optimized,
- False if a problem occurs. HErrorInfo returns more details.
<Source>: Type corresponding to the specified source Name of the HFSQL Classic data file used. <Key item>: Optional character string Name of the key item to optimize. If this parameter is not specified, <Source>.Optimize optimizes all the keys in the data file. Remarks Differences between HOptimize and HOptimizeQuery - <Source>.Optimize loads the system caches with the entire index of the data file. There is a risk of overloading the system caches if the data file is very large or if the application uses several large data files.
To avoid the risk of overload, avoid calling <Source>.Optimize on a large number of data files or key items. - HOptimizeQuery loads the system caches with only the index parts needed for the specified query (for all the data files used by the query). This function is used to optimize the queries.
Miscellaneous - <Source>.Optimize immediately gives control back to the program and is run in the background.
- <Source>.Optimize has no effect on non-key items or on data files that are not in HFSQL Classic format.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|