Readme for AMOBrowser Sample

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
This sample works only with SQL Server 2005 and SQL Server "Katmai". It will not work with any version of SQL Server earlier than SQL Server 2005.
The AMOBrowser sample lets you use Analysis Management Objects (AMO) objects to connect to a Microsoft SQL Server Analysis Services server, and then browse different AMO objects and their properties.
AMOBrowser uses a TreeView to display the AMO hierarchy and a PropertyGrid to display the properties of a selected object.


This sample shows you how to create a connection to an Analysis Services server by using AMO objects. The sample also shows you how to grab all AMO objects, together with their corresponding properties.




The Analysis Services sample uses the following items.

Application area Features
AMOAdventureWorks AMO Objects


Before you run this sample, you should have the following software installed:
  • .NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. See Installing the .NET Framework SDK in SQL Server Books Online.
  • An updated version of AdventureWorks database is also available for download on the SQL Server Developer Center Web page.
  • An updated version of the SQL Server Database Engine samples is also available for download on the SQL Server Developer Center Web page. After your sample has been successfully compiled, you will have to access one of the Analysis Services databases to test your program. We recommend that you use the AdventureWorks sample database that is provided with SQL Server.

SQL Server Business Intelligence Development Studio is not supported on computers that run the Itanium-based platform; the 64-bit development environment is supported on x64-based platforms. SQL Server samples can be modified and run on computers that run either x86 or x64-based platforms when databases used by the samples are deployed on an Itanium-based platform.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

  1. Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
  2. Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start* button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.*
  3. At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the AMOBrowser sample

  • Build the sample by using Visual Studio 2005 and the provided Visual Studio solution.— or —Build the sample by using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, and executing a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS/AmoBrowser.sln

Running the Sample

To run the AMOBrowser sample

  • In Visual Studio 2005, press F5. — or —In Visual Studio 2005, on the Debug menu, click Start.— or —At a command prompt, run a command similar to the following path: CS\AmoBrowser\bin\Debug\AmoBrowser.exe © 2007 Microsoft Corporation. All rights reserved.

Last edited Mar 6, 2007 at 7:58 PM by bonniefe, version 1


No comments yet.