Optimization in Spaix 6 – Purpose and Execution

1. What is the optimization used for?

The optimization function is designed to clean up unnecessary data records in the database and improve performance by:

• Reducing redundant entries in the Data20Values table, which in older versions were created for all filterable object properties – even those irrelevant for hydraulic selection.
• Shortening loading timeswhen opening:
  • Hydraulic selection
  • Direct product selection
• Speeding up hydraulic searches by processing fewer data records.

2. When should optimization be executed?

• After upgrading from an older Spaix version (e.g., from V5 to V6), as the data structure has changed.
• If performance issues occur, such as:
  • Slow application startup.
  • Delayed filter or search responses.
• After major data changes, e.g., after importing new pumps or series.
• The optimisation must also be performed when creating a new forward limit so that the associated values are written to Data20Values.
• Recommended: Regularly (e.g., monthly) to keep the database efficient.

3. Difference Between Optimization and Correlation Builder

Summary of Execution Order

1. Import or modify data (e.g., add new pumps).
2. Run the Correlation Builder → Generates necessary correlation data for filters and searches.
3. Run optimization (optional but recommended) → Cleans up the database for better performance.

Key Takeaway:

• If the Correlation Builder is not executed, filters, quick searches, and catalog exports will not work correctly.
• Optimization is a maintenance step that improves speed but is not mandatory for functionality.