XML for Analysis (XMLA) Reference

APPLIES TO:yesSQL Server Analysis ServicesyesAzure Analysis Services

Azure Analysis Services and SQL Server Analysis Services use XML for Analysis (XMLA) protocol for communications between client applications and an Analysis Services instance. At their most basic level, other client libraries such as ADOMD.NET and AMO construct requests and decode responses in XMLA, serving as an intermediary to an Analysis Services instance, which uses XMLA exclusively.

To support the discovery and manipulation of data in both tabular and multidimensional modes, the XMLA specification defines two generally accessible methods, Discover and Execute, and a collection of XML elements and data types. Because XML allows for a loosely coupled client and server architecture, both methods handle incoming and outgoing information in XML format.

Analysis Services is compliant with the XMLA 1.1. specification, but also extends it to include data definition and manipulation capability, implemented as annotations on the Discover and Execute methods. The extended XML syntaxes are Tabular Model Scripting Language (TMSL) and Analysis Services Scripting Language (ASSL).

TMSL is the command and object model definition syntax for tabular model databases at compatibility level 1200 and higher. TMSL communicates with Analysis Services through the XMLA protocol, where the XMLA.Execute method accepts both JSON-based statement scripts in TMSL as well as the traditional XML-based scripts in Analysis Services Scripting Language (ASSL for XMLA). To learn more, see Tabular Model Scripting Language (TMSL) Reference.

ASSL is the command and object model definition syntax for multidimensional model databases and tabular mode databases at compatibility level 1103 or lower. This definition builds on the XMLA specification without breaking it. Interoperability based on XMLA is ensured whether you use just XMLA, or XMLA and ASSL together. To learn more, see Analysis Services Scripting Language (ASSL for XMLA).

As a developer, you can use XMLA as an interface if solution requirements specify standard protocols such as XML, SOAP, and HTTP. Developers and administrators can also use XMLA on an ad-hoc basis to retrieve information from the server or run commands.

In this section

Topic Description
XML Data Types (XMLA) Describes data types in the XMLA specification.
XML Elements - Commands (XMLA) Elements that can be used within the Command element during an Execute method call.
XML Elements - Commands (XMLA) Elements that can be used within the Command element during an Execute method call.
XML Elements - Headers (XMLA) Header elements implemented by Microsoft Analysis Services.
XML Elements - Properties (XMLA) Elements to represent property information and values for XMLA headers, methods, objects, commands, and data types.
XML Elements - Methods - Discover (XMLA) Retrieves information, such as the list of available databases or details about a specific object, from an instance of Analysis Services.
XML Elements - Methods - Execute (XMLA) Sends XML for Analysis (XMLA) commands to an instance of Analysis Services.
XML Elements - Objects - DiscoverResponse (XMLA) Contains the information returned by an instance of Analysis Services in response to a Discover method call.
XML Elements - Objects - ExecuteResponse (XMLA) Contains the information returned by an instance of Analysis Services in response to an Execute method call.
XML Elements - Objects (XMLA) Objects implemented by Analysis Services.
XML for Analysis Compliance (XMLA) Describes the level of compliance with the XMLA 1.1 specification.

See also

XML for Analysis Schema Rowsets
Developing with ADOMD.NET
Developing with Analysis Management Objects (AMO)