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

KB40921: SQLCancel is not supported when running MicroStrategy reports against SAP HANA 1.0 SP2


Community Admin

• Strategy


This document explains the current behavior and interaction between MicroStrategy 9.x/10.x and SAP HANA regarding a cancel request.

When Strategy users are running multiple reports against SAP HANA 1.0 SP2 sometimes they would like to know how to cancel a request sent to the Warehouse. This document explains the current behavior and interaction between Strategy 9.x/10.x and SAP HANA regarding this topic.
 
While running a Strategy report against relational warehouses, users have the ability to cancel the statements sent to the databases directly from the Strategy Developer user interface or other methods. This action will cancel the Strategy job as well as the SQL job execution on the database side.  Users can refer to technical notes below to get additional details on how to cancel jobs in Strategy:
 
KB20098 - How to manually Cancel Jobs Submitted via Strategy Intelligence Server 9.x
KB9868 - How is query cancellation facilitated by the Strategy Query Engine?
 
However, while running reports against SAP HANA from Strategy the expected behavior is different. Users can cancel the Strategy job execution but the request on the SAP HANA side will continue executing.
 
This behavior is expected because SQLCancel ODBC call is not supported against SAP HANA 1.0 SP2.
 
Additionally, SQL_QUERY_TIMEOUT is also not supported by SAP HANA. This ODBC call is invoked by the Query Engine in response to a finite value for the following settings:
a) 'Maximum query execution time' setting at Configuration Manager > Database Instance > Database Connection > Advanced
b) 'SQL Time Out (Per Pass)' VLDB setting
 
Third Party Software Installation WARNING
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.


Comment

0 comments

Details

Knowledge Article

Published:

May 26, 2017

Last Updated:

May 26, 2017