Checking the Created SQL Text - Intergraph Smart Materials - Version 2020 (10.0) - Administration & Configuration - Hexagon PPM

Intergraph Smart Materials Classic Administration (2020)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Materials/Smart Reference Data Version
2020 (10.0)

On the A.60.07 screen, forgetting to specify all the necessary join conditions causes the most harmful situation for a query condition. On the A.06.06 screen, this type of query condition can lead to an unwanted bulk join (Cartesian product) in the SQL query created by the program associated with the Generate View button.

Sometimes a bulk join in the top level of a query may be intended; for example, you can join criteria from two tables indirectly by performing two correlated sub-queries, each one performing one comparison for the two joined criteria. However, the program cannot distinguish an intended bulk join from an unwanted one.

In such a situation, including a commented warning message in the query text can distinguish between an intended or unintended bulk join. Always check the SQL text of a new query condition view for any warning messages that may have occurred. An unintended bulk join is an extremely costly operation that can require the unnecessary use of a major portion of the database server’s I/O and CPU capacity, without producing meaningful results.