Microsoft ADOMD.

NETSDK May 10, 2004 2003-2004 Microsoft Corporation

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Contents ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1.0 Introduction 2.0 System Requirements 3.0 Installing ADOMD.NET 4.0 ADOMD.NET SDK Documentation 5.0 Post-Beta Feature Updates 6.0 Technical Issues, Known Bugs, and Limitations 7.0 ADOMD.NET now has In-Process XML for Analysis (IXMLA) 8.0 Reporting Bugs and Getting Support

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1.0 Introduction ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Microsoft SQL Server ADOMD.NET supports multidimensional data access in managed applications. ADOMD.NET is a Microsoft .NET data provider that implements the standard .NET data provider interfaces from the System.Data and System.Data.Comm on namespaces in the .NET Framework Class Library. ADOMD.NET can use any provider t hat is consistent with the Microsoft XML for Analysis Specification version 1.1, whi ch provides for universal data access to any standard data source residing over the Web, without the need to deploy a client component that exposes COM interfaces. ---NOTE--ADOMD.NET uses the XML for Analysis protocol to communicate with the server. ADOMD.NET has been tested with and is being supported in Microsoft SQL Server 20 00 Analysis Services and later releases. ADOMD.NET may also work with other XML for Analysis providers. Microsoft is not liable for or required to fix issues relate d to other XML for Analysis providers. ---------This readme provides system requirements and setup information, samples, bug reporting information, and Web resources.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2.0 System Requirements ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Before you install ADOMD.NET, your computer must meet the following requirements . These requirements are not enforced by setup. COMPUTER: Intel (Pentium 133 MHz or higher, Pentium PRO, Pentium II, or Pentium III) or compatible processor MEMORY (RAM): 64 megabytes (MB), minimum 128 MB, recommended HARD DISK SPACE: 1 MB OPERATING sYSTEM: Microsoft -orMicrosoft -orMicrosoft -orMicrosoft Mode Windows Server 2003 Windows XP with Service Pack 1 (SP1) or later Windows 2000 Server with Service Pack 1 (SP1) or later Windows NT Server 4.0 with SP6 or later with Msxml3.dll in Replace

---NOTE--For Windows NT Server 4.0, you must install the Microsoft Xmlinst.exe Replace Mode Tool because the original Microsoft XML Core Services (MSXML) used by Windows NT 4.0 does not support the XML generated by the Microsoft XML for Analysis Provider. To locate the download for the Microsoft Xmlinst.exe Replace Mode Tool, go to the Microsoft Download Center, and then search for "Xmlinst.exe Replace Mode Tool." ---------SERVICES and SOFTWARE: * Microsoft .NET Framework Class Library 1.0 SP2 or greater * MSXML 4.0 or greater * AS2000 OLE DB provider required for Microsoft Analysis Services 2000 data access * An XML for Analysis provider consistent with the XML for Analysis Specification version 1.1, such as the Microsoft XML for Analysis Provider ---NOTE--You can download the Microsoft XML for Analysis Provider from the Microsoft Download Center.

---------ACCESS PERMISSIONS: To install ADOMD.NET, you must be logged on to the computer with Local Administrator permissions.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.0 Installing ADOMD.NET ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ADOMD.NET is distributed in a self-extracting file that can be downloaded from the Internet. Before you run the installation program (ADOMD.NET.msi), make sure that your system has the required hardware and software listed previously in "2.0 System Requirements." To install the ADOMD.NET assembly, use the following procedure. To install ADOMD.NET 1. Go to the Microsoft Download Center, and then search for "ADOMD.NET" to locate the ADOMD.NET download. 2. Download the installation program, ADOMD.NET.msi, to a location on your local drive. 3. Run ADOMD.NET.msi. A wizard guides you through the installation process.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 4.0 ADOMD.NET SDK Documentation ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Online documentation is provided by the ADOMDSDK.chm file. To find the download for the ADOMDSDK.chm file, go to the Microsoft Download Center, and then search for "ADOMD.NET." Select the link that takes you to the ADOMD.NET SDK documentation.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 5.0 Post-Beta Feature Updates ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This list identifies most of the updates that have occurred since the ADOMD.NET Beta release. Because updates occurred primarily to the exposed classes and interfaces of the object model, recompiling your application will identify most of the changes that need to be implemented in order to take advantage of updates introduced since Beta. * The Level.Members property has been replaced by the Level.GetMembers method. * The Hierarchy.IsAttributeHierarchy property has been replaced by the

Hierarchy.HierarchyOrigin property. * The Hierarchy.HierarchyType property is no longer needed, and has been removed. * The Member.Children collection has been replaced by the Member.GetChildren method. * The AdomdConnection.GetOleDbSchemaTable method has been replaced by the AdomdConnection.GetSchemaDataSet method. * The AdomdCommand.ExecuteXml method has been replaced by the AdomdCommand.ExecuteXmlReader method. * The Set.DimensionCount property is no longer needed, and has been removed. * The AdomdCommand.Parameters property is no longer needed, and has removed. * The CellProperties indexer expects exactly the same string as the CellProperty.Name property returns. * The GetByName methods have been replaced by Find methods. * The AdomdConnection constructor no longer supports specifying local connections. * The MemberProperty.Name property and LevelProperty.Name property now return an unqualified name. * The MemberProperty.UniqueName property and LevelProperty.UniqueName property has been added, and returns a fully-qualified name. * The MemberPropertyCollection class and LevelPropertyCollection class are now indexed on Name, not UniqueName. * Exceptions have changed: - AdomdException, the base class for all other exceptions,represents an exception thrown by ADOMD.NET. - AdomdErrorResponseException represents an exception thrown by ADOMD.NET when the response received from a provider indicates an error. - AdomdConnectionException represents an exception thrown by ADOMD.NET when the connection could not be opened or was disconnected. - AdomdUnknownResponseException represents an exception thrown by ADOMD.NET when the response returned from the provider is not understood by ADOMD.NET. - AdomdCacheExpiredException represents an exception thrown by ADOMD.NET when a cached version of an ADOMD.NET object is no longer valid. * The following classeswere no longer needed, and were removed or hidden: AdomdArrayCollectionUtil AdomdDataTableCollectionUtil AuthenticationException BaseObject CacheBasedCollection CacheBasedFilteredCollection

CacheBasedNotFilteredCollection ConnectionException HierarchyType Kpi KpiCollection MetadataCache MixedHierarchyCollection NotFilteredCollection OnDemandDBCollectionUtil ProtectionLevel

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 6.0 Technical Issues, Known Bugs, and Limitations ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * While this ADOMD.NET Web release can accesslocal cubes in SQL Server 2000, this release cannot access local cubes in SQL Server 2005. To access local cubes in SQL Server 2005, use the SQL Server 2005 Beta releases of ADOMD.NET. * If support is required for multiple hierarchies associated with a single dimension while connected to an instance of SQL Server 2000 Analysis Services, install the hotfix described in the Microsoft Knowledge Base Article - 819609, "FIX: The XML for Analysis Services Provider Result Set Does Not Contain the Hierarchy Name" (http://support.microsoft.com/?kbid=819609).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 7.0 ADOMD.NET now has In-Process XML for Analysis (IXMLA) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The beta release of ADOMD.NET required the installation of the XML for Analysis SDK on the middle tier. With this release of ADOMD.NET, the XML for Analysis SDK is optional. If you do not wish to use an XML for Analysis provider, you can use the IXMLA capability included with ADOMD.NET. IXMLA is a DLL that ADOMD.NET will automatically load as needed. IXMLA provides the same services as the XML for Analysis SDK. To use an external XML for Analysis provider Use a connection string that uses a URL (such as "Data Source=http://localhost"). To use the internal-XML for Analysis implementation Use a connection string that does not use a URL (such as "Data Source=localhost").

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

8.0 Reporting Bugs and Getting Support ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you have questions or require support, you can access the Microsoft ADOMD newsgroup on the privatenews.microsoft.com news server to participate in discussions about Microsoft ADOMD.NET and to get peer-based support.