These tasks are scheduled with the Sinequa tool managed by the administration interface ( https://sinequa-prod.syensqo.com/form?form=jobs&datatype=jobs&dataname=jobs ). 

The information below are additional information to take note when planning the schedule for the scheduled task.

The REORGANIZE COMMAND 
The index will only be available in read-only mode during the reorganization => No indexation possible during its execution.

In the administration interface, if you set a reorganize command on different indexes, the reorganize will be run one after the other, neither in parallel nor crossed.

If you set different reorganize command for each index, you must begin the reorganize on idx_1, wait for its ending and then run the reorganize on idx_2.

To run this command, it is therefore necessary to have sufficient disk space (at least the double of the size of the index to reorganize).

THE SQL BACKUP ORDER

The BACKUP command prevents all write operations to the index. If this index size is big, the backup process may slow down the Sinequa engine in such a way that during the data writing process on disk, the engine will look as frozen for some seconds up to many minutes and consequently the Engine will stop to answer any connection request, indexation ones included. Consequently, in the engine log you may see the number of opened connections rising up to 512 and then the engine telling that the maximum number of simultaneous connection available is reached; please note that the engine is not dead, it is only buzzy. When a transaction request occurs, the transaction is put on hold until the backup operation is over. If a transaction was running when the backup operation started, the database will be backed up disregarding the operations performed since the beginning of the transaction.

BUILD LEXICON LIMT n

To use now instead of the old BUILD LEXICON order, see our documentation http//doc.sinequa.com/en.sinequa-es.v8/en.sinequa-engine.dialog-in-sql.html#section-7.5

This clause makes it possible to build or refresh a lexicon allowing the fuzzy search, search by wildcards (for a left, middle or right truncation), search by regular expressions.

This order does NOT require any reindexation. The command generates a .lext file in the index directory, that supersedes the .lex and potential .lex1. As a matter of fact, it is not compatible to use this new syntax with the previous BUILD LEXICON clause (without limit). This command depending of your parameters could lead to a performance degradation during the building of the lexicon Cf. the documentation.