SoftExpert Analytics general parameters
This content was translated using artificial intelligence. To request a review, please email documentacao_se@softexpert.com.
Prerequisites
- Access the Settings menu > General parameters (AN007).
- License Manager.
Presentation
The General Parameters menu brings together settings that control the execution and performance of analyses.
Through it, it is possible to set time limits for queries and materializations, block analyses that are slow, configure the retention of histories, manage the simultaneous execution of operations, and adjust the export port for views.
These parameter settings ensure greater stability, performance, and governance when using SoftExpert Analytics.
See how to configure the component's general parameters:
Configure general parameters
1. Access the Settings menu > General parameters (AN007).
2. Configure the system according to the desired features. The following operations are available:
Set a time limit
In the general parameters, it is possible to set a time limit for the execution of the following operations:

Executing SQL commands
By default, the timeout for executing SQL commands in SoftExpert Analytics is 5 minutes. After this time, a timeout error will occur.
To change the default time, fill in the SQL command execution timeout (minutes) field with the SQL execution timeout, which must be between 1 and 5 minutes.
• To use a time exceeding 5 minutes, additional configurations will be required on the application server. If necessary, consult technical support.
• The SQL query for an analysis is executed whenever a view is updated or dragged in the portal or view editor.
Materialization
By default, the timeout for a SoftExpert Analytics analysis is 5 minutes. After this time, a timeout error will occur.
However, for large volumes of data, it may be necessary to configure a longer time. In this case, fill in the Materialization Timeout (minutes) field with the number of minutes limit for materialization.
Data materialization is configured in the analysis, and materialization updates are performed via a schedule, which is also configured in the analysis.
When the scheduling is initiated, the system will execute the SQL query and save the data to a temporary table.
Block analyses
The system allows blocking slow analyses, making it possible to set a limit for timeout errors and the length of time they will remain blocked.
To do this, follow these steps:
1. In the Timeout section , check the Temporarily block slow analyses option .
2. In the field "Number of consecutive timeouts that block analysis" , enter the number of consecutive timeout errors that, when reached, will block the analysis.
3. In the Analysis Lock Time (minutes) field , enter the number of minutes for which the analysis will remain locked. After the defined number of minutes has elapsed, the analysis will be unlocked.

The field "Number of consecutive timeouts that block the analysis" refers to the timeouts that may occur in the analysis each time your SQL is executed; that is, if the execution of the SQL command takes too long to complete.
Manage performance
It is possible to determine whether the following operations will be executed simultaneously or not:

Materialization
To ensure that scheduled materializations run simultaneously, check the " Allow simultaneous materializations" option . It's important to note, however, that this increases the risk of overloading the servers, which could compromise the system.
If the option that allows simultaneous materializations is not selected, materializations scheduled at the same time will be executed sequentially, thus reducing the risk of overloading the servers.
The system also automates the deactivation of obsolete materializations, preventing unused analyses or those with persistent errors from continuing to consume server resources.
Two automated routines are used to disable analyses in the following scenarios:
- Unused materializations : when the materialized table is not accessed by SoftExpert Suite, for example, for 15 consecutive days.
- Materializations with recurring errors : when the analysis fails to materialize, for example, over 15 consecutive days.
Deactivating analyses is reversible: if an analysis is reused in the future, simply reactivate it and adjust its settings for it to function normally again.
The criteria for deactivation due to lack of use or recurring errors consider half the value defined in the Materializations and Views (Days) field , which defaults to 30 days.
If the materialized table is not accessed or experiences consecutive failures within 15 days, the analysis will be automatically deactivated. If necessary, this period can be extended to more than 30 days.
It is possible to enable or disable both routines using the options Automatically disable analyses with recurring errors and Automatically disable unused analyses .
The system also allows you to define the maximum number of records supported in materializations. Simply fill in the " Limit of records for materialization" field .
The default value for supported records in materializations is 1 million, and although it is possible to increase this parameter, administrators are advised to exercise caution to avoid overloading the servers and interfering with the operation of other parts of the system.
The system also allows you to configure the record limit and the maximum duration of the SQL command for generating views from the query menus.
When attempting to save a view from a query, the user may receive a prompt to apply filters to the query before proceeding with view creation.
The system displays the fields "Limit of records to generate views from query menus" and " Maximum duration of SQL command to generate views from query menus (in seconds)" , which indicate the maximum number of records (default to 1 million) and the maximum duration (default to 15 seconds) that the SQL command can take to return the query data.
If the SQL command exceeds these limits, the system will continue to prompt the user to apply filters to ensure an efficient and optimized experience.
Exports
To ensure that exports to XLSX scheduled at the same time are executed simultaneously, check the " Allow simultaneous export execution" option .
However, it is important to point out that, in this case, the risk of overloading the servers increases, which can compromise the system.
If the option that allows simultaneous exports is not selected, exports scheduled at the same time will be executed sequentially, thus reducing the risk of overloading the servers.
Queries
By default, SoftExpert Analytics is configured to allow the execution of up to 15 queries simultaneously.
To edit this setting, enter the maximum number of simultaneous queries that can be executed at the same time in the Maximum number of simultaneous queries field. The number entered must be greater than 0.
Configure history
The system allows you to configure how many days the analysis histories will remain in the database before being deleted.
To do this, in the Report View (days) and Materializations and Views (Days) fields , enter the number of days for which you want to save the history.

After the specified number of days has passed, the analysis histories will be deleted.
Define export service port
This component allows you to configure the port that will be used by the service responsible for exporting the views to images.
To do this, fill in the Export Service Port field with the port that the service should use. For SoftExpert Analytics to automatically select the port, enter the value 0.

3. Click the button
.
Conclusion
The general parameters will be properly configured.