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

SUMMARY:
This technical note documents why ‘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 Strategy Developer 9.4.x-10.10. A resolution has been provided.
SYMPTOM:
On executing a report in Strategy Developer 9.4.x-10.10, users encounter the following error:

Error: SQL Generation Complete[]QueryEngine encountered error: The generated SQL/MDX string (xxxxx bytes) is longer than the limitation of the corresponding connector (yyyyy bytes).[]Error in Process method of Component: QueryEngineServer, Project ###, Job ###, Error Code=-2147212544

• Using Strategy Developer 9.4.x-10.10, right-click on a project and select Project Configuration, as shown below:
  

• In the Project Configuration Editor, select 'VLDB Properties…' under Database instances -> SQL Data warehouses or Database instances -> MDX Data warehouses, depending on whether the error came up for a regular report or MDX report, as shown below:
  

• In the VLDB Properties Editor, expand Governing and select 'Maximum SQL/MDX Size,' as shown below:
  

• Uncheck the 'Use default inherited value - (Default Settings)' and increase the Maximum SQL/MDX Size as applicable, as shown below:
  

The options for the VLDB property are:

• 0 or -1, both default to 64000 bytes
• Any number between 1 and 999999999, this is the maximum SQL pass size in bytes
• Use default inherited value (depends on data-base)

NOTES:

• The default size may be different for different databases. It changes depending on the database instance, which is selected by the user.
• This size should be set to a value that a certified ODBC driver can handle.
• Increasing this size to a large value may risk the report failing in the ODBC driver.
• If increasing this value does not resolve the issue, then reduce the size of the SQL being generated by simplifying the report through removing attributes, metrics, and/or filters. An area to be especially aware of is importing large sets of elements for filters.

KB13674