Analysis Services Connection Type for MDX (SSRS)
To include data from an Analysis Services cube in your report, you must have a dataset that is based on a report data source of type Microsoft SQL Server Analysis Services. This built-in data source type is based on the Microsoft SQL Server Analysis Services data extension. You can retrieve metadata about dimensions, hierarchies, levels, key performance indicators (KPIs), measures, and attributes from a Microsoft SQL Server Analysis Services cube for use as report data.
This data processing extension supports multivalue parameters, server aggregates, and credentials that are managed separately from the connection string.
Use the information in this topic to build a data source. For step-by-step instructions, see Add and Verify a Data Connection or Data Source (Report Builder and SSRS).
When you connect to a Analysis Services cube, you are connecting to the database object in an Analysis Services instance on a server. The database might have multiple cubes. You specify the cube in the query designer when you build the query. The following example shows a connection string:
data source=<server name>;initial catalog=<database name>
For more connection string examples, see Data Connections, Data Sources, and Connection Strings in Report Builder.
Credentials are required to run queries, to preview the report locally, and to preview the report from the report server.
After you publish your report, you may need to change the credentials for the data source so that when the report runs on the report server, the permissions to retrieve the data are valid.
From a report authoring client, the following options are available to specify credentials:
Current Windows user (also known as integrated security).
Use a stored user name and password.
Prompt the user for credentials. This option only supports Windows integrated security.
No credentials are required. To use this option, you must have the unattended execution account configured on the report server. For more information, see Configure the Unattended Execution Account in the Reporting Services documentation in on msdn.microsoft.com.
For more information, see Data Connections, Data Sources, and Connection Strings (SSRS) or Specify Credentials in Report Builder.
After you have a data connection to an Analysis Services data source, you create a dataset and define a Multidimensional Expression (MDX) query that specifies which data to retrieve from the cube. Use the MDX graphical query designer browse and selecting from the underlying data structures on the data source.
You can specify a query in the following ways:
Build a query interactively. The Analysis Services MDX Query Designer supports the following views:
Design View Drag dimensions, members, member properties, measures, and KPIs from the metadata browser to the Data pane to build an MDX query. Drag calculated members from the CalculatedMembers pane to the Data pane to define additional dataset fields.
Query View Drag dimensions, members, member properties, measures, and KPIs from the metadata browser to the Query pane to build an MDX query. You can edit MDX text directly in the Query pane. Drag calculated members from the CalculatedMembers pane to the Query pane to define additional dataset fields.
For more information, see Analysis Services MDX Query Designer User Interface (Report Builder).
Import an existing MDX query from a report. Use the Import query button to browse to an .rdl file and import a query. You can import a query from a report that contains an embedded dataset that is based on a Analysis Services data source. Importing an MDX query directly from an .mdx file is not supported.
At design time, run the query to view a result set. The query results are automatically retrieved as a flattened rowset. The columns in the result set for a query populate the field collection for a dataset. After you build the query, view the dataset field collection that is generated from the metadata in the Report Data pane. When the report runs, the actual data is returned from the external data source.
The Analysis Services data processing extension supports extended dataset field properties. These are values that are available from the external data source but that do not appear in the Report Data pane. You can use extended field properties supported by the Analysis Services data processing extension in your report through the built-in Fields collection. For properties that have values on the data source, you can access predefined property values such as FormattedValue, Color, or UniqueName. For more information, see Extended Field Properties for an Analysis Services Database (SSRS)).
To include query parameters, create a filter in the filter area in the query designer, and mark the filter as a parameter. For each filter, a dataset is automatically created to provide the available values. By default, these datasets do not appear in the Report Data pane. For more information, see Define Parameters in the MDX Query Designer for Analysis Services (Report Builder and SSRS) and Show Hidden Datasets for Parameter Values for Multidimensional Data (Report Builder and SSRS).
By default, each report parameter has data type Text. After the report parameters are created, you might have to change default values. For more information, see Report Parameters (Report Builder and SSRS).
The Analysis Services data extension is based on the XMLA (XML for Analysis) protocol. Result sets from cubes are retrieved through the XMLA protocol as a flattened row set. Ragged hierarchies are not supported. For more information, see Ragged Hierarchies.
You can also retrieve data from an Analysis Services cube from the OLE DB data source type. For more information, see OLE DB Connection Type (SSRS).
For more information about version support, see Data Sources Supported by Reporting Services (SSRS) in the Reporting Services documentation in SQL Server Books Online.
These sections of the documentation provide in-depth conceptual information about report data, as well as procedural information about how to define, customize, and use parts of a report that are related to data.