Dr.Sum : Incorrect Result Returns when Executing Analytic Functions to Views Containing WHERE Clause

KB#: 000020891
Last Updated: 4/Feb/2021

Affected Products

• Dr. Sum V5.5 (Build = 5.5.00.0000 - 5.5.00.0020)
• Dr. Sum V5.1 (Build = 5.1.00.0000 - 5.1.00.0051)

Details

When you issue a query that contains an analytic function to a view that contains a WHERE clause,  conditional expressions in the view will not be applied. As a result, the number of rows and the output value will be incorrect.

Condition

This issue occurs when a query which contains an analytic function (OVER clause) is issued to a view that meets all of the following conditions:

• WHERE clause is set in the view.
• No summary function is in the view.
• The view is not in in-memory, or the view does not meet the requirements to be aggregated in in-memory server.

*Refer to "Conditions for in-memory server to perform summarization" in the manual of the Dr.Sum version you use. 

NOTE:

• It is not possible to issue queries containing analytic functions from Datalizer.
• It is not possible to issue queries containing analytic functions from MotionBoard except for custom views.
• Make sure that you do not use analytic functions in places where you can issue SQL directly to Dr.Sum, such as CREATE statements in views, virtual tables using Dr.Sum as data source, batch commands, self-made programs, etc.

Solution

We've released a patch to address the issue. Contact us if you've experienced the above issue.