EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics
  3. Data Engine changes in MicroStrategy 2019 release

Data Engine changes in MicroStrategy 2019 release


Matthew Pierce

Director, Cloud Support • MicroStrategy


This article discusses Data Engine changes that may impact customers when upgrading to MicroStrategy 2019.
Starting with the release of MicroStrategy ONE (March 2024), dossiers are also known as dashboards.
Data Engine Changes Impacting an Upgrade from MicroStrategy 10.4.x platform release to MicroStrategy 2019 platform release

For a more stable and robust reporting platform, MicroStrategy Data Engine has made significant changes while addressing defects and enhancements. These changes may impact upgrade from existing MicroStrategy 10.4.x platform release to new MicroStrategy 2019 platform release. These changes are reflected in the form of SQL, CSI (Cube Subsetting Instruction), and Data changes.

For the full list of changes impacting upgrade, we have categorized them based on the motivations for change. Please click on following links to know more about details of each category. Note that these are the Data Engine changes that can be observed in Upgrade Analysis Dossier.
 

Motivation for change

Data
Performance / Stability
Intuitiveness / Consistency
Security
Upgrade

 


Changes that cannot not be observed in Upgrade Analysis Dossier

There are some Data Engine changes that cannot be detected in Integrity Manager yet for SQL/Data mismatches, for example performance improvements, and hence those changes cannot not be observed in Upgrade Analysis Dossier.
Some changes can be detected in Integrity Manage but cannot be observed in Upgrade Analysis Dossier.
Please refer to following list of Data Engine Changes if Upgrade Analysis Dossier indicates a SQL/Data mismatch but does not specify a reason for such mismatch.

Internal ID

Impact

Community Article Name

Motivation For Change

Data Engine Version

MicroStrategy Version

US95205

Data

KB440048: Trailing spaces in string (e.g. attribute elements, filter) are filtered out even the "Filtering on the String Values" VLDB property is set to "Do not trim trailing space" in MicroStrategy 10.x

Consistency

2019

2019

US86780

Data

KB440049: Individual metric columns hidden with all zero or null values in MicroStrategy 10.9 through 10.11, reverted in 11.0

Intuitiveness

2019

2019

US87296

CSI, Data

KB483326: Document grids containing unrelated attributes/metrics to the group by are not displayed even if the grid contains data

Data

N/A

2019

US100554

CSI, Data

KB440215: Not Create M:M Relationship Tables when publishing MTDI cubes in memory in MicroStrategy 10.11

Data

2019

2019

DE40967

CSI, Data

KB440679: The result is incorrect when a derived attribute defined on multiple attributes with the parent of one attribute is on filter panel in MicroStrategy 10.7 and earlier

Data

N/A

2019

DE94928

Data

KB440811: When using Negative date values unexpected results are returned in MicroStrategy 10.11 and lower

Data

N/A

2019

DE92536

Data

KB442284: BigDecimal Datatype Comparison Precision Change in 11.0

Data

N/A

2019

DE79739

SQL, Data

KB442341: Using MINIMUM function to emulate LEAST function produces incorrect SQL for: Impala, BDE, Drill, Hive (1, 2), MongoDB3, and Spark1.5 in MicroStrategy 10.10 and lower

Data

N/A

2019

DE114500

SQL

KB440644: Incorrect SQL generated against sources that do not support spaces in column alias

Intuitiveness

N/A

2019

US60304

Data

KB440562: New in MicroStrategy 10.7: New value for Null checking for Analytical Engine VLDB property: Scalar operations treat nulls as zero; aggregation calculations ignore nulls

Intuitiveness

N/A

2019

DE110145

CSI, Data

KB442269: Automatic relationship detection between attributes is disabled for Data Import Intelligent Cubes creation process

Intuitiveness

N/A

2019

DE56812

Data

KB442270: Starting in MicroStrategy 10.7, the AE Null Checking VLDB Property will be turned to On by default for New Projects

Intuitiveness

N/A

2019

DE121600

SQL

KB442655:Default value changed for "Separate Count Distinct" VLDB setting for Impala 2.x database and leads to different SQL

Performance

N/A

2019

DE102494

Data

KB442283: Analytical Engine having absolute errors with double data types instead of relative errors

Data

N/A

2019

DE108284

Data

KB442284: BigDecimal Datatype Comparison Precision Change in 11.0

Performance

N/A

2019

DE48122

Data

KB483217: Users may see additional rows in grid when attribute outer join is enabled

Data

N/A

2019

DE97609

Data

KB483224: Incorrect extreme values displayed for a bar chart.

Data

N/A

2019

DE40058 

CSI

KB483234: Dossier execution suspended due to Document Linking

Performance

N/A

2019

DE67539

Data

KB483242: Smart metric defined on a New Derived Element (NDE) is calculated incorrectly when the NDE is a calculation.

Data

2019

2019

DE80858

Data

KB483251: Incorrect element displayed after using Get Report Element (GRE) with blockcount setting

Data

N/A

2019

DE96012

Data

KB483245: An empty grid with an attribute and no data is displayed.

Data

2019

2019

DE104360

Data

KB483246: XIRR metrics display no values.

Data

N/A

2019

DE84556

Data

KB483250: An Attribute with non-ID forms existing in different tables returns NULL in an Incremental Refresh Report (IRR)

Data

N/A

2019

DE99310

None

KB483248: Cascading filter does not work as expected.

Intuitiveness

2019

2019

DE64930

Data

KB483249: Document execution fails or faulty data is generated when linking two attributes.

Data

2019

2019

DE105342

SQL

KB442266 Receiving Error: "AnalysisException: all DISTINCT aggregate functions need to have the same set of parameters" when multiple count(distinct) metrics exist on a template.

Data

N/A

2019

DE114200

Data

KB442385: Data-import cube has to be re-published when the relations are modified in the cube editor

Data

2019

2019

DE144717

Data

KB483727: Document/dossier execution fails, or shows some failed visualizations, or wrong data after upgrade to 11.0 or m2019GA/U1/U2

Data

N/A

2019 Update 3



Comment

0 comments

Details

Knowledge Article

Published:

March 21, 2024

Last Updated:

March 21, 2024