Export (0) Print
Expand All

Readme_DisplayObjectNames Sample

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.

With the DisplayObjectNames sample, you can use Analysis Management Objects (AMO) objects to connect to a server that is running Microsoft SQL Server Analysis Services and then display the names of some of the AMO objects.

This sample shows how to create a connection to an Analysis Services server by using AMO objects.

The Analysis Services sample uses the following items.

Application area Features

AMOAdventureWorks

AMO Objects

Before you run this sample, you must have the following software installed:

  • .NET Framework SDK 2.0 or Microsoft Visual Studio 2005.
    You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK in SQL Server Books Online.
  • Analysis Services
  • Business Intelligence Development Studio
    ms160836.note(en-us,SQL.100).gifNote:
    Business Intelligence Development Studio is not supported on computers that run the Itanium-based operating system; the 64-bit development environment is supported on x64-based operating systems. SQL Server samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based operating system.

  • The AdventureWorks AS database.
    You can download this sample database from the Microsoft SQL Server Samples and Community Projects web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online.
  • The DisplayObjectNames sample.
    You can download this sample from the Microsoft SQL Server Samples and Community Projects Web site at http://www.codep. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online.

After your sample has been successfully compiled, you will have to access one of the Analysis Services sample databases to test your program. We recommend that you use the AdventureWorks sample database that is provided with SQL Server.

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

  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.
    ms160836.note(en-us,SQL.100).gifNote:
    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

    ms160836.note(en-us,SQL.100).gifImportant:
    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.

  • Build the sample by using Visual Studio 2005 and the provided Visual Studio solution.

    — or —

  • Build the sample using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, and run a command similar to the following at a command prompt:

    msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS/DisplayObjectNames.sln

    Other MSBuild build options can be used depending on your needs.

  • At a command prompt, run a command similar to the following:

    CS\DisplayObjectNames\bin\Debug\DisplayObjectNames.exe localhost

    The path might vary depending on the options that are used to compile the sample and your starting folder.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

Show:
© 2014 Microsoft