Troubleshooting SSAS

If the service is not responding, check the SSAS log:

image2

SSAS Log: msmdsrv.log

If one session is not responding, open an MDX window in SSMS and run the following:

SELECT * FROM   $system.discover_sessions
ORDER  BY session_used_memory DESC

image3

SSAS Sessions

If looking for active sessions, filter by:
where SESSION_STATUS=1
or
SESSION_IDLE_TIME_MS=0

Question: How To differentiate between queries and SSAS processing commands? Run a simple processing and check the SESSION_LAST_COMMAND.

If looking for heavy sessions: Identify the session by its user or its memory consumption, then check its SPID and its query from SESSION_LAST_COMMAND column, then/or cancel it:

<?xml version=“1.0” encoding=“UTF-8”?>
<cancel xmlns=“http://schemas.microsoft.com/analysisservices/2003/engine”>
<connectionid>[CID]</connectionid>
<sessionid>[SID]</sessionid>
<spid>[SPID]</spid>
<cancelassociated>[true/false]</cancelassociated>
</cancel>


image4

Cancel SSAS session

Commands belong to 1 session
Sessions belong to one connection.
A connection is run by one user and host.

To discover which connections, sessions, or commands are running, run these on an MDX screen:

SELECT * FROM $SYSTEM.DISCOVER_CONNECTIONS

SELECT * FROM $SYSTEM.DISCOVER_SESSIONS

SELECT * FROM $SYSTEM.DISCOVER_COMMANDS

Leave a Reply

Your email address will not be published. Required fields are marked *