When Strategy users are running multiple reports against MDX data sources sometimes they would like to know how to cancel an MDX statement sent to the data provider. This document explains the current general behavior and interaction between Strategy 10.x and XMLA data providers 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 Desktop user interface. This action will cancel the Strategy job as well as the SQL job execution on the database side.
However, while running MDX reports from Strategy the expected behavior is different. Users can cancel the Strategy job execution but they cannot cancel the MDX statement execution on the data provider side.
Below DSSErrors logs entries for job cancel and the XMLA logs are shown. Users can see that Strategy issue a job cancel for report execution on the Intelligence Server and "stop" logging into the XMLA log file.
DSSErrors log:
Sample Code/Error
2011-03-24 14:22:16.645-05:00 "NONE","NONE","MSAS Test Report"
2011-03-24 14:22:19.614-05:00 MSIPU::Kill: Job is created at 2011-03-24 14:22:16.332.
2011-03-24 14:22:19.645-05:00 MSIPU::Kill: PU:QueryExecution: Signalled cancellation to component task: job:267, step:4, thread:3680, will wait for timeout later.
2011-03-24 14:22:19.707-05:00 Error in executing command: StatementCancel.
2011-03-24 14:22:19.707-05:00 Unknown failed. Unable to connect.
Error type: System call error. Error communicating with connection process. Command StatementCancel; threw BaseException: . SQL Statement: with set as '{...AllMembers, ...AllMembers, ...AllMembers, ...AllMembers}'
set as '{...AllMembers}'
set as '{...AllMembers, ...AllMembers}'
set as '{...AllMembers}'
set as '{...AllMembers}'
select {.} on columns,
non empty CROSSJOIN(CROSSJOIN(CROSSJOIN(CROSSJOIN(hierarchize({}), ), hierarchize({})), ), ) on rows
from
cell properties CELL_ORDINAL, FORMATTED_VALUE, VALUE, FORMAT_STRING
.
2011-03-24 14:22:24.160-05:00 (SQL Generation CompleteJob 267 canceled.Job 267 canceled.)
Below XMLA traces during Job Canceling process:
Sample Code/Error
2011-03-24 14:22:17.848-05:00 Connecting to URL: http://sql-server-2005.labs.microstrategy.com/xmla/msmdpump.dll
2011-03-24 14:22:17.864-05:00 Post HTML message: <?xml version="1.0"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><soap:Header></soap:Header><soap:Body><Execute xmlns="urn:schemas-microsoft-com:xml-analysis"><Command><Statement><! as '{...AllMembers, ...AllMembers, ...AllMembers, ...AllMembers}'
set as '{...AllMembers}'
set as '{...AllMembers, ...AllMembers}'
set as '{...AllMembers}'
set as '{...AllMembers}'
select {.} on columns,
non empty CROSSJOIN(CROSSJOIN(CROSSJOIN(CROSSJOIN(hierarchize({}), ), hierarchize({})), ), ) on rows
from
cell properties CELL_ORDINAL, FORMATTED_VALUE, VALUE, FORMAT_STRING
]]></Statement></Command><Properties><PropertyList><Catalog>Catalog</Catalog><Format>Native</Format><AxisFormat>TupleFormat</AxisFormat><Content>Data</Content></PropertyList></Properties></Execute></soap:Body></soap:Envelope>.
2011-03-24 14:22:19.707-05:00 BEGIN: document in ExecuteResponseHandler
2011-03-24 14:22:19.801-05:00 END: SAX Parser thread
This behavior is working as design since most of the XMLA data providers do not expose MDX Cancel functionality and therefore Strategy cannot implement the MDX Cancel feature.
