AdventureWorks Cycles CLR Layer
The AdventureWorks Cycles CLR Layer sample for SQL Server 2005 provides some useful utilities that form an extra layer of functionality on top of the base AdventureWorks sample database. The first utility creates contact records for various types of people involved in the AdventureWorks database. The contact information is specified by using XML and is passed to a C#-based stored procedure. The second utility defines a Currency user-defined data type by using C#. This user-defined data type encapsulates both an amount and a culture that helps to determine the correct way to render the amount as a currency value in that culture. The third utility provides a currency conversion function that returns an instance of the Currency user-defined data type. If the AdventureWorks database has a conversion rate from U.S. dollars (USD) to the currency that is associated with the specified culture, the conversion function returns a Currency user-defined data type with the converted rate and a culture that matches the culture requested. Otherwise, a Currency user-defined data type is returned with the original amount, which should be in USD, with the en-us culture. The utilities also demonstrate how to unregister and register common language runtime (CLR) methods and assemblies by using Transact-SQL.
The exchange rates used in this sample are fictitious and should not be used for actual financial transactions.
The default installation directory is drive:\Program Files\Microsoft SQL Server\90\Samples\Engine\Programmability\CLR\AdventureWorks.
- A developer needs a convenient way to represent, persist, and manipulate different monetary amounts in different currencies.
- A developer needs a convenient way to create new contact information for employees, individual customers, store customers, and vendors and relate this information to other information stored in the AdventureWorks database.
Transact-SQL, Visual C#, and Visual Basic.
The SQLCLR layer sample uses the following features of SQL Server 2005.
CLR UDT, CLR user-defined function (UDF)
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 SamplesWeb site.
- The AdventureWorks database which is included with SQL Server 2005, and is also available at the SQL Server Developer Web site.
- The SQL Server 2005 Database Engine samples. These samples are included with SQL Server 2005. You can download the latest version of the samples at the SQL Server Developer Web site.
- .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
If you have not already created the strong-name key files, SampleKey.snk and UnsafeSampleKey.snk, generate the key files by 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 Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt.
Open a .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
At the command prompt, use the change directory (CD) command to change the current folder of the command prompt window to the Samples folder.
To determine the folder where samples are located, click Start, 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 commands to generate the key files:
sn -k SampleKey.snk
sn -k UnsafeSampleKey.snk
For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.
To build the sample, do the following:
Build the sample
Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution or by using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0. Run a command similar to the following at the command prompt:
msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS\AdventureWorksCS.sln
Ensure that the AdventureWorks database is installed.
If you did not install the SQL Server Database Engine samples in the default location, modify the path in the CREATE ASSEMBLY portion of the script in Scripts\InstallCS.sql to refer to location where the samples were installed.
If you are not an administrator for the SQL Server instance you are using, you must have an administrator grant you CreateAssembly permission to complete the installation.
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. Run the script that is contained in the file, or run a command similar to the following at the command prompt:
sqlcmd -E -I -i Scripts\InstallCS.sql
This script performs the following actions:
- Removes any stored procedures that are about to be defined if they exist.
- Drops the assembly registration if it already exists.
- Registers the assembly.
- Registers the CLR stored procedures.
Running the Sample
To run the sample, do the following:
Run the sample
Load the Scripts\test.sql file in Management Studio and run it. Or, run the following command at the command prompt:
sqlcmd -E -I -i Scripts\test.sql
Removing the Sample
Use the following procedure to remove the SQLCLR Layer sample:
Remove the sample
Load and run Scripts\cleanup.sql in Management Studio. Or, run the following command at the command prompt:
sqlcmd -E -I -i Scripts\cleanup.sql
The CLR for SQL Server 2005 or SQL Server 2005 Express Edition 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.
Help and Information
5 December 2005