Updated: 5 December 2005
This sample program lets you browse the hierarchy of SMO objects by using Microsoft .NET reflection. It shows how exactly SQL Server Management Objects (SMO) represent database objects with all their collections and properties.
Microsoft .NET reflection reflects SMO objects and collections directly, which is useful to test because it lets you see exactly what properties and collections are there, and what their values are, without writing any test code. Most of the functionality comes
from the property grid that you can see on the right side. By using the property grid, you can see all properties with their values, and examine named properties.
Samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples. Sample applications and assemblies
should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.
This sample requires that the following components are 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.
- SQL Server 2005 Integration Services (SSIS).
- The sample package and data files that it uses must be installed on the local hard disk drive.
- The AdventureWorks OLTP database must be installed.
- The AdventureWorks database must be attached.
- You must have administrative permissions on the AdventureWorks database. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.
If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\90\Samples\Engine\Programmability\SMO\SmoBrowser
The C# solution for the code sample is located in the CS directory, and the Visual Basic solution is located in the VB directory.
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
- 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.
- 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 2005, 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\90\Samples.*
- 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.
Building and using the sample using the Command Line Compiler
- Open a .NET Framework or Microsoft Visual Studio 2005 command prompt. Use the change directory (CD) command to change the current directory of the command prompt window to the solution directory that you want to work in.
- Type the following command to build either the C# or the Visual Basic version of the sample:
for /r %f in (*.sln) do msbuild.exe "%f"
Building and using the sample from Microsoft Visual Studio 2005 (optional)
- From the File menu in Microsoft Visual Studio 2005, click Open, click
Project, and then open SmoBrowser.sln in the solution directory that you want to work in.
- Press F5, or click Start on the Debug menu to compile and run the project.
|5 December 2005
||Changed content: Changed instructions for generating a key file, including the name and location of the key file.
© 2007 Microsoft Corporation. All rights reserved.