cancel
Showing results for 
Search instead for 
Did you mean: 

Query optimizer generated too many subcubes in the query plan

former_member244885
Participant
0 Kudos

Hi,

I'm helping a consultant who'd having an issue with a report.  I've pulled the following error message from tbllogs:

"Query optimizer generated too many subcubes in the query plan"

Has anyone ever seen this error message?

Here's the full details:

==============[System Exception Tracing]==============

[System  Name] : SQE

[Message Type] : ErrorMessage

[Job Name]     : clsSUAccess::getOlapData

[DateTime]     : 05/16/2016 16:30:10

[UserId]       : ...

[Exception]

    DetailMsg  : {Error: Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Query optimizer generated too many subcubes in the query plan.

   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.Execute(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)

   at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteXmlReader()

   at DataService.OSoft.Services.Webservice.SharedQueryEngine.clsSUAccess.getOlapData(StringBuilder& sbResult, String[]& sMultiHQry, Hashtable& hsDimsIndex, Hashtable[]& hsAxisLists, String& sRetMsg, String& sWhere, Boolean bCheckSecurity)}

==============[System Exception Tracing  End ]==============

Accepted Solutions (0)

Answers (1)

Answers (1)

april_shultz
Participant
0 Kudos

Hi Jon,

This error is an  MS SQL Analysis error and will appear when executing a huge MDX query. Analysis server has a limitation on the sub cube size, they may need to minimize the query size.

Thanks

April

former_member244885
Participant
0 Kudos

It looks like the error, "Query optimizer generated too many subcubes in the query plan", from tbllogs, is a symptom of overloading epmretrieve.