The InProcessDataAccess sample contains a number of simple functions that demonstrate various features of the SQLCLR in-process data access provider.

Note:
When you compile common language runtime integration samples, the path of the version of the Microsoft .NET Framework compiler that was distributed with SQL Server 2005 must be the first Framework directory in the PATH environment variable. The location of the compiler that is included with SQL Server 2005 is either drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx or drive:\Windows\Microsoft.NET\Framework\v2.0.xxxxx, where drive is the installation drive and xxxxx is the version of the .NET Framework that is included with SQL Server 2005.

The default installation directory is drive:\Program Files\Microsoft SQL Server\90\Samples\Engine\Programmability\CLR\InProcessDataAccess

Scenario

A developer would like to access data from CLR-based components deployed on the server.

Languages

Transact-SQL, Visual C#, and Visual Basic.

Features

The InProcessDataAccess sample uses the following features of SQL Server 2005:

Application Area Features

Overall

CLR

Prerequisites

Before running this sample, make sure the following software is installed:

  • SQL Server 2005 or SQL Server 2005 Express Edition (SQL Server Express). You can obtain SQL Server Express free of charge from the SQL Server 2005 Express Edition Documentation and Samples Web site.

  • The AdventureWorks database, which is included with SQL Server 2005, and is also available at the SQL Server 2005 Express Edition Documentation and Samples Web site.

  • The SQL Server 2005 Database Engine samples. These samples are included with SQL Server 2005, and are also included with the Microsoft Microsoft .NET Framework version 2.0 SDK 2.0.

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

Building the Sample

To build the sample, do the following:

Build the sample

  1. CD to the install directory and execute the following at a .NET Framework or Microsoft Visual Studio 2005 command prompt:

    sn -k temp.snk

  2. Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution, or by using , which is included in the .NET Framework SDK 2.0, by executing a command similar to the following at the command prompt:

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

  3. Ensure that the AdventureWorks database is installed, or, if necessary, create the database in which you want to install the samples.

  4. Open the scripts\installCS.sql or scripts\installVB.sql file, depending on whether you compiled the Visual C# project or the Visual Basic project, in SQL Server Management Studio, and execute the script that is contained in the file, or execute a command similar to the following at the command prompt:

    sqlcmd -E -I -i Scripts\InstallCS.sql

    This file contains the script needed to install and register the in-proc samples into SQL Server.

Running the Sample

To run the sample, do the following:

Run the sample

  1. Open the scripts\test.sql file in SQL Server Management Studio and execute the script that is contained in the file, or execute the following command at the command prompt:

    sqlcmd -E -I -i Scripts\test.sql

    This script invokes the in-process data access samples from Transact-SQL.

Removing the Sample

To remove the sample, do the following:

Remove the sample

  1. Open the scripts\cleanup.sql file in SQL Server Management Studio and execute the script that is contained in the file, or execute the following command at the command prompt:

    sqlcmd -E -I -i Scripts\cleanup.sql

    This script removes the sample.

Comments

The CLR for SQL Server 2005 or SQL Server Express must be enabled for this sample to work correctly.

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.