Click here to Skip to main content
15,897,273 members
Articles / Web Development / IIS

Microsoft Analysis Services 2005: Displaying a grid using ADOMD.NET and MDX

Rate me:
Please Sign up or sign in to vote.
4.76/5 (21 votes)
19 Aug 2008CPOL9 min read 130.5K   3.4K   61  
The article explains how to fetch data from Microsoft Analysis Services 2005 (OLAP) Cube using ADOMD.NET and MDX, and display it in the form of a grid.
<?xml version="1.0"?>
<!-- 
    Note: As an alternative to hand editing this file you can use the 
    web admin tool to configure settings for your application. Use
    the Website->Asp.Net Configuration option in Visual Studio.
    A full list of settings and comments can be found in 
    machine.config.comments usually located in 
    \Windows\Microsoft.Net\Framework\v2.x\Config 
-->
<configuration>
	<appSettings/>
	<connectionStrings/>
	<system.web>
		<!-- 
            Set compilation debug="true" to insert debugging 
            symbols into the compiled page. Because this 
            affects performance, set this value to true only 
            during development.
        -->
		<compilation debug="true">
			<assemblies>
				<add assembly="Microsoft.AnalysisServices.AdomdClient, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91"/></assemblies></compilation>
		<!--
            The <authentication> section enables configuration 
            of the security authentication mode used by 
            ASP.NET to identify an incoming user. 
        -->
		<authentication mode="Windows"/>

		<!--
		<identity impersonate ="true" userName="user" password="password"/>
		-->
		
		<!--
            The <customErrors> section enables configuration 
            of what to do if/when an unhandled error occurs 
            during the execution of a request. Specifically, 
            it enables developers to configure html error pages 
            to be displayed in place of a error stack trace.

        <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />
        </customErrors>
        -->
	</system.web>
</configuration>

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Architect Nexvisionix Inc.
India India
Click here to email Hitesh

Hitesh lives in Mumbai, INDIA and works with Nexvisioinix, one of the leaders in providing solutions based on Microsoft BI technologies. (For more information on Nexvisionix visit www.nexvisionix.com)

Since year 2003, he has been working on Microsft .NET and BI technologies such as Microsoft Analysis Services 2005. He is also proficient in MDX.

Comments and Discussions