|
|
|
|
|
- Overview
- WDOptimizer includes multiple modes to optimize indexes:
- How to?
- Optimizing the indexes of a data file
- Re-indexing options
- Overview
- Advanced reindexing mode
- Options for compressing the memos
- Options
- Access rights to the data file
WDOptimizer: Index optimization
 Available only with these kinds of connection
WDOptimizer includes multiple modes to optimize indexes: 1. Check indexes Checks consistency between index and data files. 2. Optimize index speed (Recalculate statistics) Optimize indexes by calculating index statistics. These statistics are used to optimize the filters, the queries and the HFSQL views. Note: The more the data file is modified, the less the statistics reflect the content of the HFSQL data file.. The more records the data file contains, the less the modification of a single record impacts the overall statistics. 3. Reconstruct indexes Optimize access to data file records and recalculate statistics. All the crossed records are automatically deleted. 4. Rebuild indexes and memos Optimizes the entire data file, its indexes and memos. 5. Revise and compress indexes and memos Optimize the entire data file, index and memos. The memos will be compressed. Advanced options are available ("Options for compressing the memos"). Remarks: - The data file is recreated: the last write date of the last record (obtained by function HRecordDate) is reset to the current date.
- Timestamp items are also modified and are set to the date and time at which the optimization is performed.
Remarks: - Apart from option 2, all the optimization modes lock the data files during the optimization. The users are informed that the data file is currently under maintenance.
- Once the reindexing is performed, the current HFSQL context is restored (except if the option for compressing memos was chosen).
Optimizing the indexes of a data file To optimize the indexes of a data file: - Start WDOptimizer:
- Directly from WINDEV, WEBDEV or WINDEV Mobile: in the "Tools" pane, in the "Database" group, click on "WDOptimizer".
- run "WDOptimizer.EXE" directly.
- Select the data files to process. You can:
- Drag and Drop the data files from the explorer to WDOptimizer. The dropped files automatically appear in the list.
- add one or more data files using the "Add a file" button.
- add the data files found in a directory via the "Add a folder" button.
To process the sub-directories, select "When adding a directory, include the files of all the sub-directories".
- Select the data files to process and indicate (if necessary) the password of each data file.
Note: If the password is identical for all data files, check the "The password is the same for all files" option. - Click the "Optimize indexes" or "Optimize indexes of selected files" button and choose the desired option.
A report is generated if a problem occurs. Overview The re-indexing options are displayed in the lower part of the screen: Advanced reindexing mode These options are taken into account for the re-indexing operations from type 1 to type 4: - Delete inactive records (deleted or crossed records)
If this option is selected, the crossed records are permanently deleted. Reminder When a record is crossed out, it is logically deleted and may be recovered at a later date. The record is still found in the data file. Deleting the crossed records deletes these records permanently and optimizes the size of data file. - Delete damaged records
If this option is checked, the damaged records are automatically deleted. - Reindex without locking the client computers
If this option is checked, the re-indexing operation is performed in background task and the client applications are not stopped. Attention: This option is only taken into account for HFSQL Client/Server data files.. - Density of the index
Corresponds to the density rate of the indexes. This rate is set to 80 by default. A higher rate increases the density of the index and reduces its size. In this case, the browses, searches, filters and queries are faster. The additions of records and the modifications of records may be slower. A smaller rate reduces the density of the index and increases its size. In this case, iterations, searches, filters and queries will be slower. The additions of records and the modifications of records will be faster. Please note: this parameter can only be used on data files in HFSQL Classic or Client/Server format. - Charset
The character set of the data file is kept by default. However, a re-indexing operation can be performed by changing the character set of the data file. In this case, the new character set will be taken into account during the re-index operation. Sorts, searches, etc. on string keys (strings, characters, date and time) will be performed according to this character set.
Options for compressing the memos These options are taken into account during the revision with compression of indexes and memos (option 5): - Keep crossed records
If this option is selected, the crossed records are kept. Otherwise, they are permanently deleted. - Try to retrieve data from memo if damaged
If this option is selected, WDOptimizer tries to retrieve the memo. Otherwise, the damaged records are retrieved without the associated memo. Attention Memo recovery may be partial. Check your data files.
Options These options simplify management of the list of data files to be re-indexed: - The password is the same for all files
If this option is selected, the same password is used for all the data files. All you have to do is specify the password in the "Password" column of the first data file found in the list. If this option is unchecked, the password will have to be specified in the "Password" column of the table for each data file. - When adding a directory, include the files found in all the subdirectories
If this option is selected, the data files found in the sub-directories are automatically added.
Access rights to the data file The optimization triggers the recreation of the data file on disk. Check the rights of the optimized data file. These rights may differ from those of the original data file. In this case, they must be redefined in Windows after the optimization.
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|