Analysis Services Data Access Interfaces (SSAS)
Microsoft SQL Server 2005 Analysis Services (SSAS) supports several technologies that can be used to access data and metadata stored on an instance of Analysis Services. Using the Analysis Services data access technologies, you can do the following:
Retrieve Schema Rowsets
Schema rowsets are one way in which client applications can examine metadata stored on, and retrieve support and monitoring information from, an Analysis Services instance. You can retrieve OLE DB, OLE DB for Online Analytical Processing (OLAP), OLE DB for Data Mining, or XML for Analysis (XMLA) schema rowsets.
To retrieve schema rowsets:
- You can use OLE DB commands with the Analysis Services 9.0 OLE DB provider. For more information, see Analysis Services 9.0 OLE DB Provider (SSAS).
- You can run the XMLA Discover method directly against an Analysis Services instance to retrieve schema rowset information. For more information, see Discover Method (XMLA).
Retrieve Data and Metadata
You can retrieve data and metadata, in either tabular or multidimensional formats, from cubes and mining models.
To retrieve data and metadata:
- You can use ADOMD.NET in a managed client application to retrieve Analysis Services information using common Microsoft .NET Framework data access interfaces. For more information, see ADOMD.NET.
- You can use the Analysis Services 9.0 OLE DB provider in unmanaged client applications to support OLE DB access. For more information, see Analysis Services 9.0 OLE DB Provider (SSAS).
- You can use XMLA to retrieve data directly from an Analysis Services instance in an XML-based format. For more information, see XML for Analysis (XMLA).
Manipulate Analysis Services Objects
You can manipulate Analysis Services objects, such as databases, cubes, dimensions, and mining structures, using Multidimensional Expressions (MDX), Data Mining Extensions (DMX), or XMLA commands.
To manipulate Analysis Services objects:
- You can use ADOMD.NET in a managed client application to send commands using common .NET Framework data access interfaces. For more information, see ADOMD.NET.
- You can use the Analysis Services 9.0 OLE DB provider in unmanaged client applications to send commands using OLE DB access. For more information, see Analysis Services 9.0 OLE DB Provider (SSAS).
- You can use XMLA to send commands directly to an Analysis Services instance. For more information, see XML for Analysis (XMLA).
In This Section
Describes the OLE DB, OLE DB for OLAP, OLE DB for Data Mining, and XMLA schema rowsets supported by Analysis Services.
Describes the XMLA protocol, used to communicate with an Analysis Services instance.
XMLA takes advantage of SOAP to provide direct access to Analysis Services through an XML-based open standard for multidimensional data access.
Describes the native OLE DB provider for Analysis Services.
Describes ADOMD.NET, the set of namespaces in the .NET Framework that provide access to data and metadata on an Analysis Services instance.
[!NOTA] This section describes the following APIs: Microsoft.AnalysisServices.AdomdClient.dll, msmgdsrv.dll, and msolap90.dll. Only these APIs are supported by Microsoft for accessing Analysis Services data.
Microsoft .NET Framework Support
Starting with SQL Server 2005, Analysis Services fully supports the Microsoft .NET Framework. Support of the .NET Framework lets developers access Analysis Services data and metadata using a choice of .NET-compliant languages or by using native code. The Microsoft .NET Framework SDK includes the Microsoft Visual Basic .NET and Microsoft C# compilers, as well as related tools.
To create applications that use Analysis Services, developers can use Microsoft Visual Studio .NET—an integrated design environment (IDE) that offers developers many tools and features that simplify and accelerate the iterative cycles of coding, debugging, and testing, and deployment. However, developers do not have to use Visual Studio .NET to compile and build managed applications for Analysis Services. Developers can use any code or text editor that is compatible with the .NET Framework.
|By default, the .NET Framework is installed with SQL Server 2005, but the .NET Framework SDK is not. Without the SDK installed on your computer and included in the Books Online collection, links to SDK content in this section will not work. Install the .NET Framework SDK. After you install the SDK, add the SDK to the Books Online collection and table of contents by following the instructions in Administrador de la colección de ayuda combinada de SQL Server 2005.|