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

KB47062: An error ‘The generated SQL/MDX string (xxxxxxx bytes) is longer than the limitation of the corresponding connector (65536 bytes)’ is generated when running a report with a custom group object in MicroStrategy Developer and Web 9.4.x-10.x.


Stefan Zepeda

Salesforce Solutions Architect • Strategy


When a custom group object is used in a report, depending on the length of the definition, many ‘case when’ expressions may be generated in its SQL.

SYMPTOM:
When a custom group object is used in a report, depending on the length of the definition, many ‘case when’ expressions may be generated in its SQL. This could result in the error as follows:
 


Error: SQL Generation Complete
QueryEngine encountered error: The generated SQL/MDX string (xxxxxxx bytes) 
is longer than the limitation of the corresponding connector (65536 bytes)..
Error in Process method of Component: QueryEngineServer, 
Project Strategy Tutorial, Job 148, Error Code= -2147212544.

 
CAUSE:
This issue occurs because the governing limit of the 'Maximum SQL/MDX Size' VLDB property (which specifies the SQL size on a pass-by-pass basis) is exceeded. The Maximum SQL/MDX Size is the Maximum size of SQL string accepted by a certified ODBC driver (bytes).
 
ACTION:
Users can apply one of the options below to avoid this error from being generated.
1. As described in KB13674: ‘The generated SQL/MDX string (xxxxx bytes) is longer than the limitation of the corresponding connector (yyyyy bytes)’ error occurs when executing a report in MicroStrategy Developer 9.4.x-10.x , increase the value of the ‘Maximum SQL/MDX Size’ VLDB property
2. Change the VLDB property ‘SQL Global optimization’ to Level 1 to avoid using the ‘case when’ expression, which could reduce the size of individual SQL statements, so the report SQL may not exceed the specified maximum SQL size.
3. Revise the custom group definition to reduce the elements of it so that a shorter SQL will be generated.

KB47062


Comment

0 comments

Details

Knowledge Article

Published:

May 17, 2017

Last Updated:

January 8, 2019