Ending User Activity
An administrator of Microsoft SQL Server Analysis Services may want to end user activity as part of workload management. You do this by canceling sessions and connections. Sessions can be formed automatically when a query is run (implicit), or named at the time of creation by the administrator (explicit). Connections are open conduits over which queries can be run. Both sessions and connections can be ended while they are active. For example, an administrator may want to end processing for a session if the processing is taking too long or if some doubt has arisen as to whether the command being executed was written correctly.
Ending Sessions and Connections
Because there is no user interface for managing sessions and connections, the administrator uses the Cancel command through the XMLA EXECUTE METHOD to end a session or connection. Ending a session stops all commands that are running as part of that session. Ending a connection closes its host session. However, Analysis Services is not able to close a connection if it cannot track all the sessions that are open by it, for example, when multiple sessions are opened in an HTTP scenario. For more information about the XMLA EXECUTE METHOD, see Execute Method (XMLA).
See Also