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

KB35113: "Problem calling SQLExecute, Possible reason is Database selected is inconsistent with the selected Data Source Name" error message is received when querying the WH catalog through the Query Builder interface in MicroStrategy Developer 9 and 10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


"Problem calling SQLExecute, Possible reason is Database selected is inconsistent with the selected Data Source Name" error message is received when querying the WH catalog through the Query Builder interface in MicroStrategy Developer 9 and 10.x

SYMPTOM:
In Strategy Developer 9 and 10.x, when users launch the Query Builder interface and click on “All available tables” they receive the following message
 

ka02R000000kZsTQAU_0EM440000002Dt7.jpeg

"Problem calling SQLEXecute,  Possbile reason is Database selected is inconsistent with the selected Data Source Name.  Check the Database type in section Define data connection."
 
 
CAUSE:
 
When retrieving tables from a Hive data source, Strategy must use standard ODBC calls instead of SQL statements.This option can be set in the warehouse catalog, but is not available through Query Builder.  So when a user attempts to retrieve tables through Query Builder, Strategy will submit a SQL statement, resulting in the error message above.
 
ACTION:
 
Users can add the tables to the project through the warehouse catalog.  After this is done, the tables will already be available in the Query Builder interface.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 5, 2017

Last Updated:

June 5, 2017