Upgrade impact | MSTR Version / Data Engine Version | Upgrade Engine Tag(s) | Choice available to Customers |
Performance degradation only. SQL/Data remains unchanged. Change was done in DE182339 and Doc was done in US330322 | 2020 U3 / NA | Not tagged but documented. | - Accept the new performance change. |
Performance degradation in some cases when DISTINCT TUPLE is generated in CSI Table Join Tree even if there is no real join happening for in-memory cube. Data remains unchanged. | 2020 / 2019 | DE123254 | - Accept the new behavior. |
Performance degradation in cases when we add additional attributes in Table Join Tree output level in CSI to produce better data. SQL and Data also changes. | 10.5 / NA | DE4097 | - Accept the new correct data. |
For Live datasets only. The code changes the order of the selected attributes and then change the join path in the FROM clause for the SQL. So a different join path is generated and since the derived attribute is involved in Data Engine Version 2020, the performance degrades. No derived attribute push down, the code change will cause sql mismatch and potential performance change. fix is part of F9810 so there is no special tag for this change but now we need explicit tag to pinpoint this change. SQL and Data also changes. | 2020 / 2020 | DE128512 | - Accept the new correct data. |
For projects containing too many attributes (say 30K), the performance degradation may be observed for documents/dossiers with report as dataset. In Amica CUVP, performance degradation is seen from 30 secs to 1 min. Active investigation to see if we can improve the performance via DE190615 | 2021 / 2021 | F25102 | - Accept the new behavior. |
