Tabular Model Data Access
Tabular model databases in Analysis Services can be accessed by most of the same clients, interfaces, and languages that you use to retrieve data or metadata from a multidimensional model. For more information, see Multidimensional Model Data Access (Analysis Services - Multidimensional Data).
This topic describes the clients, query languages, and programmatic interfaces that work with tabular models.
The following Microsoft client applications support native connections to Analysis Services tabular model databases.
You can connect to tabular model databases from Excel, using the data visualization and analysis capabilities in Excel to work with your data. To access the data, you define an Analysis Services data connection, specify a server that runs in tabular server mode, and then choose the database you want to use. For more information, see Connect to or import data from SQL Server Analysis Services.
Excel is also the recommended application for browsing tabular models in SQL Server Data Tools (SSDT). The tool includes an Analyze in Excel option that starts a new instance of Excel, creates an Excel workbook, and opens a data connection from the workbook to the model workspace database. When browsing tabular model data in Excel, be aware that Excel issues queries against the model using the Excel PivotTable client. Accordingly, operations within the Excel workbook result in MDX queries being sent to the workspace database, not DAX queries. If you are using SQL Profiler or another monitoring tool to monitor queries, you can expect to see MDX and not DAX in the profiler trace. For more information about the Analyze in Excel feature, see Analyze in Excel (SSAS Tabular).
Power View is a Reporting Services reporting client application that runs in a SharePoint 2010 environment. It combines data exploration, query design, and presentation layout into an integrated ad-hoc reporting experience. Power View can use tabular models as data sources, regardless of whether the model is hosted on an instance of Analysis Services running in tabular mode, or retrieved from a relational data store by using DirectQuery mode. To connect to a tabular model in Power View, you must create a connection file that contains the server location and database name. You can create a Reporting Services shared data source or a BI semantic model connection file in SharePoint. For more information about BI semantic model connections, see Power Pivot BI Semantic Model Connection (.bism).
The Power View client determines the structure of the specified model by sending a request to the specified data source, which returns a schema that can be used by the client to create queries against the model as a data source and perform operations based on the data. Subsequent operations in the Power View user interface to filter data, perform calculations or aggregations, and display associated data are controlled by the client and cannot be programmatically manipulated.
The queries that are sent by the Power View client to the model are issued as DAX statements, which you can monitor by setting a trace on the model. The client also issues a request to the server for the initial schema definition, which is presented according to the Conceptual Schema Definition Language (CSDL). For more information, see CSDL Annotations for Business Intelligence (CSDLBI)
You can use SQL Server Management Studio to manage instances that host tabular models, and to query the metadata and data in them. You can process models or the objects in a model, create and manage partitions, and set security that can be used for managing data access. For more information, see the following topics:
You can use both the MDX and XMLA query windows in SQL Server Management Studio to retrieve data and metadata from a tabular model database. However, note the following restrictions:
Statements using MDX and DMX are not supported for models that have been deployed in DirectQuery mode; therefore, if you need to create a query against a tabular model in DirectQuery mode, you should use an XMLA Query window instead.
You cannot change the database context of the XMLA Query window after you have opened the Query window. Therefore, if you need to send a query to a different database or to a different instance, you must open that database or instance using SQL Server Management Studio and open a new XMLA Query window within that context.
You can create traces against an Analysis Services tabular model as you would on a multidimensional solution. In this release, Analysis Services provides many new events that can be used to track memory usage, query and processing operations, and file usage. For more information, see Analysis Services Trace Events.
If you put a trace on a tabular model database, you might see some events that are categorized as DMX queries. However, data mining is not supported on tabular model data, and the DMX queries executed on the database are limited to SELECT statements on the model metadata. The events are categorized as DMX only because the same parser framework is used for MDX.
Analysis Services tabular models support most of the same query languages that are provided for access to multidimensional models. The exception is tabular models that have been deployed in DirectQuery mode, which do not retrieve data from an Analysis Services data store, but retrieve data directly from a SQL Server data source. You cannot query these models using MDX, but must use a client that supports conversion of DAX expressions to Transact-SQL statements, such as the Power View client.
You can use DAX for creating expressions and formulas in all kinds of tabular models, regardless of whether the model is stored on SharePoint as a Power Pivot-enabled Excel workbook, or on an instance of Analysis Services.
Additionally, you can use DAX expressions within the context of an XMLA EXECUTE command statement to send queries to a tabular model that has been deployed in DirectQuery mode.
For examples of queries on a tabular model using DAX, see DAX Query Syntax Reference.
You can use MDX to create queries against tabular models that use the in-memory cache as the preferred query method (that is, models that have not been deployed in DirectQuery mode). Although clients such as Power View use DAX both for creating aggregations and for querying the model as a data source, if you are familiar with MDX it can be a shortcut to create sample queries in MDX, see Building Measures in MDX.
The Conceptual Schema Definition Language is not a query language, per se, but it can be used to retrieve information about the model and model metadata, that can later be used to create reports or create queries against the model.
For information about how CSDL is used in tabular models, see CSDL Annotations for Business Intelligence (CSDLBI).
The principal interfaces that are used for interacting with Analysis Services tabular models are the schema rowsets, XMLA, and the query clients and query tools provided by SQL Server Management Studio and SQL Server Data Tools.
You can retrieve data and metadata from tabular models in managed applications using ADOMD.NET. For examples of applications that create and modify objects in a tabular model, see the following resources:
Tabular Model AMO Sample on Codeplex
AdventureWorks samples on CodePlex
You can use the Analysis Services 9.0 OLE DB provider in unmanaged client applications to support OLE DB access to tabular models. An updated version of the Analysis Services OLE DB provider is required to enable tabular model access. For more information about providers used with tabular models, see Install the Analysis Services OLE DB Provider on SharePoint Servers .
You can also retrieve data directly from an Analysis Services instance in an XML-based format. You can retrieve the schema of the tabular model by using the DISCOVER_CSDL_METADATA rowset, or you can use an EXECUTE or DISCOVER command with existing ASSL elements, objects, or properties. For more information, see the following resources:
You can create, modify, delete, and process tabular models and objects in them, including tables, columns, perspectives, measures, and partitions, using XMLA commands, or by using AMO. Both AMO and XMLA have been updated to support additional properties that are used in tabular models for enhanced reporting and modeling.
For examples of how tabular objects can be scripted using AMO and XMLA, see the following resources:
Tabular Model AMO Sample on Codeplex
AdventureWorks Samples on CodePlex
You can use PowerShell to manage and monitor instances of Analysis Services, as well as for creating and monitoring security used for tabular model access. For more information, see Analysis Services PowerShell.
Client applications can use the schema rowsets to examine the metadata of tabular models and to retrieve support and monitoring information from the Analysis Services server. In this release of SQL Server new schema rowsets have been added and existing schema rowsets extended to support features related to tabular models and to enhance monitoring and performance analysis across Analysis Services.
New schema rowset for tracking dependencies among the columns and references in a tabular model
New schema rowset for obtaining the CSDL representation of a tabular model
New schema rowset for monitoring SQL Server Extended Events. For more information, see Use SQL Server Extended Events (XEvents) to Monitor Analysis Services.
New Type column lets you filter traces by category. For more information, see Create Profiler Traces for Replay (Analysis Services).
New STRUCTURE_TYPE enumeration supports identification of user-defined hierarchies created in tabular models. For more information, see Hierarchies (SSAS Tabular).
There are no updates to the OLE DB for Data Mining schema rowsets in this release.
You cannot use MDX or DMX queries in a database that has been deployed in DirectQuery mode; therefore, if you need to execute a query against a DirectQuery model using the schema rowsets, you should use XMLA, and not the associated DMV. For DMVs that return results for the server as a whole, such as SELECT * from $system.DBSCHEMA_CATALOGS or DISCOVER_TRACES, you can execute the query in the content of a database that is deployed in a cached mode.