Export (0) Print
Expand All
4 out of 16 rated this helpful - Rate this topic

ADOMD.NET Client Programming

The ADOMD.NET client components reside within the Microsoft.AnalysisServices.AdomdClient namespace (in microsoft.analysisservices.adomdclient.dll). These client components provide the functionality for client and middle-tier applications to easily query data and metadata from an analytical data store, such as Microsoft SQL Server 2005 Analysis Services (SSAS).

Before you begin using the ADOMD.NET client components, you should become familiar with the client functionality, object model, and release differences.

For more information: ADOMD.NET Client Functionality, ADOMD.NET Client Object Architecture, ADOMD.NET Release Differences, Migrating From ADO MD To ADOMD.NET

In querying an analytical data source, there are a set of common tasks that need to be performed. The following table represents the common tasks in which you use the ADOMD.NET client objects to perform such a query.

Task Description

Establishing Connections in ADOMD.NET

In ADOMD.NET, you use an AdomdConnection object to establish connections with analytical data sources, such as Analysis Services databases. You can use the AdomdConnection object to run commands, retrieve data, and retrieve metadata from the analytical data source.

Retrieving Metadata from an Analytical Data Source

After a connection has been established, you can use a wide variety of objects to retrieve information about the underlying data source. This functionality allows applications to adapt to the data source to which they have connected.

Executing Commands Against an Analytical Data Source

The AdomdCommand object provides the interfaces necessary for running commands against the underlying analytical data source.

Retrieving Data from an Analytical Data Source

After a command runs, data could be retrieved and parsed using either the CellSet, AdomdDataReader, or System.XmlReader objects.

Performing Transactions in ADOMD.NET

All of the actions listed in the previous rows of this table can take place within a read-committed transaction, in which shared locks are held while the data is being read to avoid dirty reads. The data can still be changed before the end of the transaction, resulting in non-repeatable reads or phantom data. The AdomdTransaction object provides the transaction functionality in ADOMD.NET.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.