- Detailed characteristics of a HyperFileSQL Classic database
- "Description" tab
- "SQL" tab
- "Backups" tab
- "Maintenance" tab
- "Management of .REP" tab
- "Transactions" tab
Managing HFSQL Classic databases
Available only with this kind of connection
From version 17
, this feature is not available anymore: it is no longer possible to describe an HFSQL Classic application.
The HyperFileSQL Control Center proposes a full management of the HyperFileSQL Classic databases.
To display the characteristics of a HyperFileSQL Classic database:
- Add a HyperFileSQL Classic application if necessary.
- Select the name of the desired application in the "HyperFileSQL Classic" pane of the Control Center.
- Select the name of the desired deployment directory.
- The right section of Control Center displays the different tabs used to manage the characteristics of the HyperFileSQL Classic database.
Detailed characteristics of a HyperFileSQL Classic database
This tab presents the information regarding the data files of the selected analysis.
The following information is displayed:
- The logical/physical file name
- The type of the file
- The total size of the file
- The number of active records
- The number of crossed records
- The number of deleted records
- The total number of records (active, crossed and deleted)
- Whether the file is password-protected
- Whether the file is encrypted
- Whether the log process is enabled for this file
- Whether the replication is enabled for this file, ...
You also have the ability to get some information about the links.
Remark: This feature is only available for applications for which an analysis has been specified.
This tab is used to run a SQL query on the data found in the database. To do so, enter the SQL code of the query and click "Run".
You also have the ability to copy the SQL code of a query into the clipboard.
This tab is used to perform and restore backups of database files.
A list of files is generated for each deployment directory. By default, this list contains all the data files.
This list can be modified to save only the desired elements.
A .LST file is generated for each list of files saved by clicking the "Save a list" button.
The "Save" button is used to start the backup. This backup is performed in a file in WDZ format. In the window that is opened, specify:
- the backup directory.
- the name of the backup (that is also the name of the backup sub-directory). This sub-directory does not necessarily have to be created.
- whether the files are compressed: an archive in WDZ format is created. This archive can be a multi-volume archive.
- whether the indexes must be saved. The size of the backup will be reduced if the indexes are not saved. The indexes can be rebuilt by the reindexing.
- whether the data files must be locked during the backup (recommended to avoid saving inconsistent data).
The "Restore" button is used to restore an existing backup. All you have to do is select the directory of the backup.
This tab is used to re-index the data files of the database.
To perform a maintenance operation on the data files of the database:
- Check the data files that must be processed. Specify (if necessary) the password of the files to process.
Remark: If the password is identical for all the data files, check "The password is identical for all the files".
- Select the options and the type of optimization to perform:
- Start the reindex operation via the "Start optimizing the indexes of selected files" button.
The available options are as follows:
- Advanced reindexing mode
These options are taken into account for the re-indexing operations from type 1 to type 4:
- Delete the inactive records (deleted or crossed)
If this option is selected, the crossed records are permanently deleted.
Reminder: When a record is crossed, it is deleted logically and it can be retrieved later. 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 the damaged records
If this option is checked, the damaged records are automatically deleted.
- Density of the index
Corresponds to the density rate of 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, the browses, searches, filters and queries will be slower. The additions of records and the modifications of records will be faster.
Caution: This parameter can only be used on the data files in HyperFileSQL Classic or Client/Server format.
- Character set
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. The sorts, the searches, ... 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 the crossed records
If this option is selected, the crossed records are kept. Otherwise, they are permanently deleted.
- Attempt to retrieve data from the memo if it is damaged
If this option is selected, WDOptimizer tries to retrieve the memo. Otherwise, the damaged records are retrieved without the associated memo.
Caution: The memo may not be entirely retrieved. Check your data files.
- Types of optimization
- Option 1. Check the indexes: Checks the consistency between the index and the data files.
- Option 2. Optimize the speed of indexes (recalculating the stat): Optimizes the indexes by calculating statistics on the indexes. These statistics are used to optimize the filters, the queries and the HyperFileSQL views.
Remark: The more the data file is modified, the less the statistics reflect the content of the HyperFileSQL data file. The more records the data file contains, the less the modification of a single record impacts the overall statistics.
- Option 3. Rebuild the indexes: Optimizes the access to the records of the data file and re-calculates the statistics. All the crossed records are automatically deleted.
- Option 4. Rebuild the indexes and the memos: Optimizes the entire data file, its index and its memos.
- Option 5. Check and compress the indexes and the memos: Optimizes the entire data file, its index and its memos. The memos will be compressed. Advanced options are available ("Options for compressing the memos").
- 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.
Caution: This option is taken into account for the HyperFileSQL Client/Server data files only.
"Management of .REP" tab
This tab allows you to manage the .REP file used to localize the data handled by the application.
Select the .REP file of your application.
- add new data files
- delete data files, ...
This tab is used to transform the records in transaction into standard records.
This page is also available for…
Click [Add] to post a comment