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

KB483881: After upgrading to MicroStrategy 2019, queries requiring temporary tables in Google BigQuery generate SQL containing repeated table aliases


Caitlin Corrigan

Senior Education Developer • Strategy


This article explains why SQL containing repeated table aliases is being generated by Google BigQuery. This article also provides steps to generate the correct syntax for Google BigQuery reports that utilize temporary tables, including multi-source reports.

Description

Strategy 2019 supports the creation of temporary tables in Google BigQuery. However, even after following the steps provided in the Google BigQuery whitepaper. users may encounter the following error:
"Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [42000:70: on SQLHANDLE] [Strategy][BigQuery] (70) Invalid query: Syntax error: INSERT target cannot have an alias at [1:39]"
Viewing the report's SQL, the insert statement is generated as below:
"Insert into MSTR_TMP.ZZOP00 MSTR_TMP.ZZOP00 values (XXX, XXX, XXX)"

ka02R000000g5FKQAY_0EM2R000000nAHa.jpeg

Why is this happening? 

This error is a known defect in Strategy 2019 General Availability, Update 1, and Update 2, due to changes made in supported versions of Google BigQuery that require column names in insert statements. 
 

Solution

For versions of Google BigQuery that do not require the column names inside of an insert statement, you should upgrade to Strategy 2019 Update 3 or higher, and then upgrade the Google BigQuery DBMS object. For instructions on updating the Google BigQuery DBMS objects, please see KB43537: How to install DBMS objects provided by MicroStrategy Technical Support. 
Viewing the report's SQL, the insert statement is generated as below:
"Insert into 'MSTR_TMP'.ZZOP00 values (XXX,XXX,XXX)"

ka02R000000g5FKQAY_0EM2R000000nAJR.jpeg

For versions of Google BigQuery that do not require the column names inside of an insert statement, upgrade to Strategy 2020. 
Viewing the report's SQL, the insert statement is generated as below:
"Insert into MSTR_TMP.ZZO (Column 1, Column 2, Column 3) values (XXX, XXX, XXX)"

ka02R000000g5FKQAY_0EM2R000000nAJv.jpeg

Comment

0 comments

Details

Knowledge Article

Published:

December 16, 2019

Last Updated:

December 16, 2019