Microsoft SQL Server Product Samples: Engine

Source code checked in, #11622

ReedMe — Wed, 11 Jun 2008 05:42:45 GMT

Adding 'Katmai:June 2008 RC0'

Updated Wiki: SS2008!Readme_VerifyBackup

bonniefe — Wed, 11 Jun 2008 00:24:45 GMT

Readme_VerifyBackup Sample

6/10/2008 1:32:27 AM

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.
This sample demonstrates techniques for verifying a backup on a backup device to ensure the data can be used to restore the appropriate databases. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users select the backup device and verify the contents of the selected backup. This sample provides a user interface that lets the user specify the SQL Server instance to connect to and whether to use Windows Authentication. The user can then select which database and backup file location and name.
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.

Requirements

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 Documentation.
Integration Services.
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.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\VerifyBackup
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, 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.
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 VerifyBackup.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. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2005!Readme_VerifyBackup

bonniefe — Wed, 11 Jun 2008 00:24:17 GMT

Readme_VerifyBackup

6/10/2008 4:38:07 PM

Updated: 5 December 2005
This sample demonstrates techniques for verifying a backup on a backup device to ensure the data can be used to restore the appropriate databases. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users select the backup device and verify the contents of the selected backup. This sample provides a user interface that lets the user specify the SQL Server instance to connect to and whether to use Windows Authentication. The user can then select which database and backup file location and name.
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.

Requirements

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.
Microsoft SQL Server 2005 Integration Services.
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.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

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\VerifyBackup
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, 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.
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 VerifyBackup.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.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2008!Readme_UtilityConversion

bonniefe — Wed, 11 Jun 2008 00:23:31 GMT

Readme_UtilityConversion Sample

6/10/2008 1:32:27 AM

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.
This sample demonstrates techniques for implementing assembly functions (SQLCLR) in database applications. By using SQL Server common language runtime (CLR) capabilities of Microsoft SQL Server, this application lets users run CLR assembly code from within SQL Server. This sample provides sample code to perform various datatype conversions.
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.

Requirements

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 Documentation.
Integration Services.
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.
This sample is used by the LoadRegAssembly.exe from the LoadRegAssembly project. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\UtilityConversion
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, 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.
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 UtilityConversion.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. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2005!Readme_UtilityConversion

bonniefe — Wed, 11 Jun 2008 00:23:11 GMT

Readme_UtilityConversion

6/10/2008 4:38:07 PM

Updated: 5 December 2005
This sample demonstrates techniques for implementing assembly functions (SQLCLR) in database applications. By using SQL Server common language runtime (CLR) capabilities of Microsoft SQL Server, this application lets users run CLR assembly code from within SQL Server. This sample provides sample code to perform various datatype conversions.
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.

Requirements

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.
Microsoft SQL Server 2005 Integration Services.
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.
This sample is used by the LoadRegAssembly.exe from the LoadRegAssembly project. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

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\UtilityConversion
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, 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.
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 UtilityConversion.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.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2008!Readme_Tracer

bonniefe — Wed, 11 Jun 2008 00:22:51 GMT

Readme_Tracer Sample

6/10/2008 1:32:27 AM

This sample demonstrates techniques for implementing profile trace from the local instance of SQL Server to the output console. Using SQL Server Trace Management objects (TMO), this console application can be used to display trace information from the local instance of SQL Server.
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.

Requirements

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 Documentation.
Integration Services.
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.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\Tracer
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, 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.
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 Tracer.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. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2005!Readme_Tracer

bonniefe — Wed, 11 Jun 2008 00:22:31 GMT

Readme_Tracer

6/10/2008 4:38:07 PM

Updated: 5 December 2005
This sample demonstrates techniques for implementing profile trace from the local instance of SQL Server to the output console. Using SQL Server Trace Management objects (TMO), this console application can be used to display trace information from the local instance of SQL Server.
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.

Requirements

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.
Microsoft SQL Server 2005 Integration Services.
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.

Location

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\Tracer
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, 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.
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 Tracer.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.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2008!Readme_SqlService

bonniefe — Wed, 11 Jun 2008 00:22:14 GMT

Readme_SqlService Sample

6/10/2008 1:32:27 AM

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.
This sample demonstrates techniques for requesting SQL Server services in database applications. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users query the services of the selected server. This sample provides a user interface that permits specifying the SQL Server instance to connect to. The user can then request the services.
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.

Requirements

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 Documentation.

Integration Services.
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.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\SqlService
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, 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.
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 SqlService.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. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2005!Readme_SqlService

bonniefe — Wed, 11 Jun 2008 00:21:51 GMT

Readme_SqlService

6/10/2008 4:38:07 PM

Updated: 5 December 2005
This sample demonstrates techniques for requesting SQL Server services in database applications. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application lets users query the services of the selected server. This sample provides a user interface that permits specifying the SQL Server instance to connect to. The user can then request the services.
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.

Requirements

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.
Microsoft SQL Server 2005 Integration Services.
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.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

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\SqlService
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, 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.
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 SqlService.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.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2008!Readme_SqlServerList

bonniefe — Wed, 11 Jun 2008 00:21:00 GMT

Readme_SqlServerList Sample

6/10/2008 1:32:27 AM

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.
This sample demonstrates two techniques for retrieving a list of computers that are running SQL Server on the network to the list boxes.
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.

Requirements

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 Documentation.
Integration Services.
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.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\SqlServerList
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, 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.
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 SqlServerList.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. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2005!Readme_SqlServerList

bonniefe — Wed, 11 Jun 2008 00:20:22 GMT

Readme_SqlServerList

6/10/2008 4:38:07 PM

Updated: 5 December 2005
This sample demonstrates two techniques for retrieving a list of computers that are running SQL Server on the network to the list boxes.
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.

Requirements

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.
Microsoft SQL Server 2005 Integration Services.
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.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

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\SqlServerList
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, 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.
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 SqlServerList.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.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2008!Readme_SMOPing

bonniefe — Wed, 11 Jun 2008 00:18:58 GMT

Readme_SmoPing Sample

6/10/2008 1:32:27 AM

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.
This sample demonstrates techniques for requesting a SQL Server login in a console database application. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application connects to the selected server.
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.

Requirements

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 Documentation.
Integration Services.
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.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\SmoPing
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, 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.
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 SmoPing.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. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2005!Readme_SMOPing

bonniefe — Wed, 11 Jun 2008 00:18:29 GMT

Readme_SmoPing

6/10/2008 4:38:07 PM

Updated: 5 December 2005
This sample demonstrates techniques for requesting a SQL Server login in a console database application. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application connects to the selected server.
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.

Requirements

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.
Microsoft SQL Server 2005 Integration Services.
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.

Location

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\SmoPing
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, 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.
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 SmoPing.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.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2005!ReadMe_SmoEvents

bonniefe — Wed, 11 Jun 2008 00:17:40 GMT

ReadMe_SmoEvents

6/10/2008 4:38:07 PM

Updated: 5 December 2005
This sample demonstrates techniques for displaying SQL Server events in a console database application. By using SQL Server Management Object (SMO) capabilities of Microsoft SQL Server, this application connects to the server on which the program is executing.
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.

Requirements

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.
Microsoft SQL Server 2005 Integration Services.
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.

Location

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\SmoEvents
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 clickSDK 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, 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.
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 SmoEvents.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.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2008!Readme_SmoCompare

bonniefe — Wed, 11 Jun 2008 00:17:20 GMT

Readme_SmoCompare Sample

6/10/2008 1:32:27 AM

This sample demonstrates techniques for implementing a comparison of two database objects. By using SQL Server Management Objects (SMO), the application lets the user compare property and schema information for two objects. The application demonstrates the general object properties, iteration through properties, and exception handling for errors relating to object 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.

Requirements

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 Documentation.
Integration Services.
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.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\SmoCompare
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, 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.
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 SmoCompare.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.

Comments

The following types of database objects have been tested with this sample. Comparing other kinds of database objects is not supported.

Database
Table
Stored Procedure
View
User
Schemas
UserDefinedFunction
Role
Endpoint
JobServer © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2005!Readme_SmoCompare

bonniefe — Wed, 11 Jun 2008 00:17:02 GMT

Readme_SmoCompare

6/10/2008 4:38:07 PM

Updated: 17 July 2006
This sample demonstrates techniques for implementing a comparison of two database objects. By using SQL Server Management Objects (SMO), the application lets the user compare property and schema information for two objects. The application demonstrates the general object properties, iteration through properties, and exception handling for errors relating to object 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.

Requirements

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.
Microsoft SQL Server 2005 Integration Services.
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.
You must compile the ServerConnect component first, because this sample has a dependency on the ServerConnect sample. For more information about how to install samples, see "Installing Sample Integration Services Packages" in SQL Server Books Online.

Location

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\SmoCompare
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, 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.
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 SmoCompare.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.

Comments

The following types of database objects have been tested with this sample. Comparing other kinds of database objects is not supported.

Database
Table
Stored Procedure
View
User
Schemas
UserDefinedFunction
Role
Endpoint
JobServer

Change History

Release	History
17 July 2006	Changed content: Added comments section and information about which kinds of database objects are supported.
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2008!Readme_SmoBrowser

bonniefe — Wed, 11 Jun 2008 00:16:42 GMT

Readme_SmoBrowser Sample

6/10/2008 1:32:27 AM

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.
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.

Requirements

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 Documentation.
Integration Services.
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.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\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, 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.
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.

Updated Wiki: SS2005!Readme_SmoBrowser

bonniefe — Wed, 11 Jun 2008 00:16:26 GMT

Readme_SmoBrowser

6/10/2008 4:38:07 PM

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.

Requirements

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.

Location

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, 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.
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.

Change History

Release	History
5 December 2005	Changed content: Changed instructions for generating a key file, including the name and location of the key file.

Updated Wiki: SS2008!Readme_ServiceBrokerConfiguration

bonniefe — Wed, 11 Jun 2008 00:16:07 GMT

Readme_ServiceBrokerConfiguration Sample

6/10/2008 1:32:27 AM

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.
This sample shows how to create Service Broker objects by using SQL Server Management Objects (SMO). The sample is implemented because several Windows User Controls and classes necessary to create Service Broker objects.
The sample is targeted at a Microsoft .NET Framework developer who wants to learn how to use Service Broker SMO and learn how to create Windows User Controls to manage SQL Server objects. The core scenario is a Microsoft .NET Framework developer who is creating a custom Service Broker management application.
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.

Requirements

This sample requires that the following components are installed.

.NET Framework SDK 2.0. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework Documentation.
SQL Server Database Engine.

Location

If the code sample was installed to the default location, the sample is located in the following directory:
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\ServiceBrokerConfiguration
The C# solution for the code sample is located in the CS 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, 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.
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.

If you are using the Microsoft .NET Framework SDK, do the following:

Build the Visual Studio Solution

Click Start, point to All Programs, point to Microsoft .NET Framework SDK v2.0, and then click SDK Command Prompt.
Locate the root folder of the sample. Type the following command for the default location:
C cd \Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\SMO\ServiceBrokerConfiguration\CS\

Type the following to build the Visual Studio solution:
msbuild Or, if you are using Visual Studio 2005, do the following:

Open the \CS\ConfigurationComponent.sln solution file.
Press F6 to build the solution.

Set up SQL Server sample database and sample XML schemas

Locate the \CS\Script folder.
Open and run setup.sql from within SQL Server Management Studio.If you are setting up Remote Service Binding:

Set up SQL Server master keys (optional)

Locate the \CS\Script folder.
Open masterkey.sql from within SQL Server Management Studio.
Enter a password for the master database key in the CREATE MASTER KEY ENCRYPTION BY PASSWORD = statement.
Enter a password for the ssb_ConfigurationSample database key in the CREATE MASTER KEY ENCRYPTION BY PASSWORD = statement.
Run masterkey.sql.

Running the Sample

To run the sample

The default location for the C# version is C:\Program Files\Microsoft SQL Server\100\Samples\SMO\ServiceBrokerConfiguration\CS\SampleApplication\bin\Debug\SampleApplication.exe.

To connect to a local SQL Server instance

Enter a server name in the Server Name field, or accept the default (local) server name.
Click Connect.

To configure the sample for a new database.

Click Options on the Objects tab.
Enter a ScriptPath, or accept the default path. The ScriptPath is used to export a script to a file.
Click Create. The Create button configures the sample, including setting the BaseUrn.

To create MessageTypes

Click New, and then click MessageType.**
Enter ShippingRequest for the MessageType name.
Click Create to create the new MessageType, click New, and then click Message Type.
Enter ShippingAccept for the MessageType name.
Click Create to create the new MessageType, click New, and then click Message Type.
Enter ShippingComplete for MessageType name.
Click Create to create the new MessageType.

To create a contract

Click New, and then click Contract.
Select the MessageTypeMappings drop-down menu.
Select all MessageTypes created above.
Select Target for ShippingAccept and ShippingComplete MessageSource.
Close the MessageTypeMappings drop-down menu.
Enter Shipping for the contract name.
Click Create to create a new contact.

To create queues

Click New, and then click Queue.
Enter ClientQueue for the queue name.
Click Create to create the new queue, click New, and then click Queue.
Enter ServerQueue for queue name.
Click Create to create the new queue.

To create services without RemoteServiceBinding enabled

Click New, and then click Service.
Enter ClientService for the service name.
Select the ContractNames drop-down menu and select the Shipping contract.
Select the QueueName drop-down menu and select the ClientQueue queue.
Enter or select a ServiceOwnerName.
Click Create to create the new service, and then click New.
Enter ServerService for the service name.
Select the ContractNames drop-down and select the Shipping contract.
Select the QueueName drop-down menu and select the ServerQueue queue.
Enter or select a ServiceOwnerName.
Click Create to create the new service.

To create services with RemoteServiceBinding enabled

Click New, and then click Service.
Enter RemoteService for the service name.
Select the ContractNames drop-down menu and select the Shipping contract.
Set EnableRemoteService to true.
Select the QueueName drop-down menu and select the ClientQueue queue.
Enter or select a ServiceOwnerName.
Click Create to create the new service, and then click New.

To enable anonymous access for a Remote Service

Select RemoteService within the object tree.
Set AllowAnonymous to True.
Click Alter to alter the service.

To create a Target Instance Endpoint

Click New, and then click Target Instance Endpoint.
Enter a name, or accept the default name.
Click Create.

To set a script export path

Click the Object tab if this tab is not already active.
Click Options.
Enter a valid ScriptPath.
Click Create.

To export an object

Select an object within the objects tree.
Click Script then Export.
The object is exported to the ScriptPath set in Application Configuration.

To export a Service definition to a file

Select a service from within the Objects tree.
Click Script, and then click Export.
The service script is exported to the ScriptPath set in Application Configuration.

To drop an object

Select the object in the TreeView.
Click either Drop or Edit, Drop {ObjectName}.

To alter an object

Click the object in the Objects tree that you want to modify.
Modify the properties of that object.
Click Alter to alter the object.

To query data describing an object

Each object can output data describing the object to a Textbox and/or DataGrid.
Select an object in the TreeView.
Click Query.

Removing the Sample

To drop services

Click the ClientService node.
Drop the object.
Click the ServerService node.
Drop the object.

To drop queues

Click the ClientQueue node.
Drop the object.
Click the ServerQueue node.
Drop the object.

To drop contracts

Click the Shipping contract node.
Drop the object.

To drop MessageTypes

Click the ShippingRequest MessageType node.
Drop the object.
Click the ShippingAccept MessageType node.
Drop the object.
Click the ShippingComplete MessageType node.
Drop the object.

To drop a Target Instance Endpoint

Click a Target Instance Endpoint node.