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

KB19867: “Error: SQL Generation Complete. Internal error happens in Calculation” error message appears when a metric performs a rank on a metric based on the maximum value of a textual attribute form in MicroStrategy Developer 9.x and 10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


Error: SQL Generation Complete. Internal error happens in Calculation” error message appears when a metric performs a rank on a metric based on the maximum value of a textual attribute form in MicroStrategy Developer 9.x and 10.x

SYMPTOM:
When a user creates a metric that calculates the rank of a second metric object based on the maximum value of a textual attribute form, and the warehouse database does not provide rank function implementation, an error is received when a report containing the metric object is executed:
 

ka02R000000kVdQQAU_0EM440000002Edw.jpeg

 
Error: SQL Generation Complete. Internal error happens in Calculation. Error in Process method of Component: QueryEngineServer, Project <Project_Name>, Job xxxx, Error Code = -2147212287.
The issue can be reproduced in Strategy Tutorial by following these steps:
 

  • Create a metric object that returns the Maximum value of an attribute form of type Text:
ka02R000000kVdQQAU_0EM440000002Ee5.jpeg
  • Create a metric object that performs a rank on the metric created on step 1
ka02R000000kVdQQAU_0EM440000002Ee2.jpeg
  • Create a report including the attribute used in the metric defined in step 1 and the metric created in step 2:
ka02R000000kVdQQAU_0EM440000002Ee0.jpeg
  • Execute the report. The error specified above is returned.

CAUSE:
This is a known issue with Strategy Developer 9.x and 10.x
 
ACTION:
Contact Strategy Technical Support for an update on this issue
 
WORKAROUND:
Users can implement two different workarounds:
 

  1. Use a database type that provides an implementation of ranking functions (i.e. SQL Server, Oracle, etc.)
  2. Perform the ranking over a numeric attribute form.

Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

May 30, 2017