Reading data from the cube in Analysis Services from RDLC

In the RDL of Microsoft's in-service, the default is to support querying data from the RDLC cube, but there is an indirect way to access the cube's data.

The relative RDL and RDLC are completely different routines. The difference between the two is definitely not the name on only a C so simple, from the design of the details and deployment of the way there are great differences. The actual project is often based on different circumstances to specific decisions to use which option.

There are two ways to access this recommendation.

The first approach is to link the Analysis Services database to the Data Engine service in the form of links, and then the logic of the MDX query is written to the stored procedure, and the final top-level application indirectly achieves the access to the Analysis service database by invoking the stored procedure.

Another option is to encapsulate the data source with a method. Because the RDLC itself is in a C # or vb.net project, it is supported to use a method of the project as a data source in RDLC so that the adomd.net can be called in the method and the MDX result is returned to RDLC as a list.

The implementation of the first method can refer to the operation of SQL Server linked servers, which is mainly described in the second method.

To install SQL Server, the procedure can refer here.

Http://www.cnblogs.com/aspnetx/archive/2012/04/13/2446479.html

The installation of version 2012 is recommended here. You don't have to worry too much about whether or not the previous version will migrate without considering the new features in 2012.

Download the sample data file.

Download from CodePlex.

DW File:

http://msftdbprodsamples.codeplex.com/downloads/get/165405

SSAS script file:

http://msftdbprodsamples.codeplex.com/downloads/get/258486

Since the cube used in this article is taken from the Adventure Works sample library in Microsoft's official SQL Server example, and the SSAS database provides only project files, the DW file needs to be downloaded at the same time for SSAS to process.

It is important to note that the DW database is being downloaded, not the OLTP database, and the two libraries are structurally different and do not download incorrectly.

The downloaded database file is first attached to the Data Engine service.