Click here to Skip to main content
Click here to Skip to main content

Execute .NET Code under SQL Server 2005

, 26 Aug 2007 CPOL
Rate this:
Please Sign up or sign in to vote.
Article describes all the problems and constraints defined to use managed code under SQL Server 2005.


First of all, I would like to congratulate the Microsoft Development Team for their superb and innovative technology using which we can use managed code written in any of the .NET supported languages in Microsoft SQL Server 2005 Stored Procedures. If I make it simple, then "Now you can call any function written in .NET class library in your SQL Server stored procedure". This technology will allow us to use the features of .NET language with the extendibility of SQL Server.


I got an article of using MSMQ from SQL Server in CodeProject written by a gentlemen regarding MSMQ, and Messaging was used from SQL SP. I tried to show the constraints and limitations of using such assemblies and the required configuration in SQL Server 2005, so that the developers can begin. And I am sharing the practical problems which I faced in the actual implementation of this.

Before starting, you have to enable the managed code execution feature of the SQL Server which is disabled by default. To enable it, execute the following code as a query in your SQL Server query editor.

sp_configure 'clr enable', 1

Now your server is ready to run managed code under its runtime. But let me tell you it's not magic but it's the same technology being used by the .NET framework. The only important part is that now SQL Server is also able to execute code on CLR. Isn't it great? Before writing this article, I did a lot of research on this. I got several articles explaining the same. But I faced a lot of problems because things were scattered. Now I am trying to simulate the whole procedure in this article. I did this study because of my specific requirements. I was using Message Queuing Service of Microsoft in C# .NET. But after some time, I got a requirement in which I needed to send a message from a Stored Procedure to MSMQ Queue. And till that time for me it was possible by using the System. Messaging namespace of .NET runtime only. I know most of the developers are wondering about MSMQ. Don't worry, I won't go into details of that right now. We will start with a simple application which will use a simple string returning function of C# .NET class library. Let's start with the class library.

  • Start .NET 2005 Studio.
  • Open a new class library.
  • Select C# as the language.
  • Name the project as ManagedCodeAndSQLServer.
  • By default, you will find a class named Class1.cs created for you.
  • Rename it as BaseFunctionClass.cs.

Create a simple function in the class as follows:

using System;
using System.Collections.Generic;
using System.Text;
using System.IO;
using System.Data.SqlTypes;
using System.Data.SqlClient;
using Microsoft.SqlServer.Server;

namespace ManagedCodeAndSQLServer
    public class BaseFunctionClass
        #region "Default Constructor"
        public BaseFunctionClass()

        #region "Welcome Function"
        /// <summary>
        /// This function will be called from the SQL Stored Procedure.
        /// </summary>
        /// <param name=""strName"">Name</param>
        /// <returns>Welcome Message</returns>
        public static void GetMessage(SqlString strName, out SqlString  
          strMessge = "Welcome," + strName + ", " + "your code is getting
          executed under CLR !";


Important Points

I hope you are able to notice some new things in the above code. First of all, the [SqlProcedure] attribute on the GetMessage function intimates the CLR that the function is callable from SQL Server Stored procedure. The things that I am telling you are my own experiences; you may not find these things in articles published on the Internet. When using a CLR function, you must remember that the SQL server nvarchar is equivalent to System.String. But the most important part is that "CLR enabled procedure can only return Int32, Int and void data types". That's why I have used output parameter with the GetMessage function. Also I have used SqlString instead of System.String. Please keep all the above things in mind.

Now build the project and leave it because your work from the .NET class library point of view is over. Now come to your SQL Server again. I hope you still remember that we enabled CLR integration in our server at the start of the article. If not, then don't wait for me to come and enable it.

We have to register ManagedCodeAndSQLServer.dll as an assembly in our database. To register the assembly, you should have owner rights in your database or you should be the local system admin or Server Admin. The assemblies that we are going to register should be registered in UnSafe mode. Otherwise they would not be able to access resources external to SQL Server 2005. And to register an unsafe assembly, you should have 'unsafe' rights enabled in your username or role. All the above things are very important so take care of them, otherwise you won't be able to register your assembly. So create a database 'TestingCLR'. Before registering the .NET assembly in the database, you have to set the trustworthy option of the database on using the following code:


Now register ManagedCodeAndSQLServer.dll under that using the following code:

FROM 'E:\Important\SQL\ManagedCodeAndSQLServer\ManagedCodeAndSQLServer\bin\

I am again saying if the dbo is not having 'unsafe assembly' right, it won't work. Similarly if I am using a specific class of .NET in my DLL, I have to register it prior to DLL registration in the same way. For example, I am using System.Messaging in my assembly, then I have to register it using the following code:

FROM 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Messaging.dll'

To use the normal functionality, we need not register the DLL from .NET runtime as in our case. Now in your server explorer, go to your TestingCLR database, select Programmability and in Assemblies, you will find an assembly registered with the name given by you, i.e., "HelloDotNet". Now you are almost done. You should know the full path (namespace convention) of the function that you are going to use from that assembly. In our case, it is: ManagedCodeAndSQLServer.BaseFunctionClass and GetMessage is our function to be used. Now I am creating a simple Stored Procedure to use this assembly as follows:

CREATE PROCEDURE usp_UseHelloDotNetAssembly
@name nvarchar(200),
@msg nvarchar(MAX)OUTPUT
AS EXTERNAL NAME ManagedCodeAndSQLServer.[ManagedCodeAndSQLServer.

To execute the procedure:

DECLARE @msg varchar(MAX)
EXEC usp_UseHelloDotNetAssembly 'Kittu And Tannu',@msg output
PRINT @msg

You will get the following output: Welcome, Kittu And Tannu, your code is getting executed under CLR !

Try it and enjoy!


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Kamal Singh Kharayat
Technical Lead Government of Dubai
United Arab Emirates United Arab Emirates
Technology is ever-changing; the best approach to deal with the competition is self-learning…..
A strong self-learner and skilled programmer having 7+ years of experience is delivering, managing and deploying state of art applications in Microsoft .Net & SharePoint technologies.
An excellent team player and understands his role in any project responsibly.
Having experience in leading projects technically with a Team Size of 5+ developers, understanding the needs of clients and end users well. Owns experience in Project Architecture Design, Requirement gathering, analysis and based on the Project needs practiced many development models, primarily Waterfall and Agile.
“A good application development always leads to Feasibility, Reliability, Scalability and more importantly usability from End user prospect”
Specialties: Competent technologist in the field of Microsoft .NET and SharePoint Technologies.
Available for Corporate training in SharePoint Development and Administration across UAE.
"Improvement is the only thing which makes me happy...."
e-mail Addresses:
skype id: stek_ks
Follow on   Twitter   Google+   LinkedIn

Comments and Discussions

QuestionSystem.NullReferenceException: at TwilioSMS.SMS.ListarMensajes(String& respuesta) PinmemberRonnie Rios2-Oct-14 13:07 
AnswerRe: System.NullReferenceException: at TwilioSMS.SMS.ListarMensajes(String& respuesta) PinmemberRonnie Rios3-Oct-14 7:43 
GeneralMy vote of 5 PinmemberАslam Iqbal4-Mar-14 20:54 
GeneralMy vote of 5 PinmemberHimanshuJain6-Feb-14 6:22 
GeneralMy vote of 5 Pinmemberabeethadesilva7-Aug-13 9:36 
GeneralMy vote of 5 PinmemberMember 255869716-Jan-13 18:16 
QuestionNice tutorial Pinmemberdonpp4623-Nov-12 2:08 
GeneralMy vote of 5 Pinmembere.BISHOP12-Oct-12 8:31 
GeneralMy vote of 5 PinmvpKanasz Robert25-Sep-12 23:46 
QuestionSuperb article!!!...Very few People Know how to run .Net code from SQL PinmemberPunny16-May-12 0:28 
QuestionWaking up a windows service on a remote server from T-SQL using .NET CLR Pinmembermtrudel27-Mar-12 4:52 
QuestionProblems with your explanation PinmemberMember 235697716-Mar-12 10:46 
GeneralMy vote of 5 Pinmemberneo_monty15-Nov-10 23:53 
GeneralYour Job is really good PinmemberPradip.Kumar.Meta18-Jun-10 23:04 
GeneralRe: Your Job is really good PinmemberKamal Singh Kharayat19-Jun-10 3:00 
GeneralProblem with sqlstring execution. Pinmembervvr1514-Apr-10 20:11 
GeneralExcellent article. udf calling external function - need help PinmemberMember 22538551-Apr-10 11:14 
GeneralTransaction code Pinmemberkaams28-Feb-10 20:55 
QuestionNaming Error? Pinmembersmcintyr_1126-Oct-09 13:21 
AnswerRe: Naming Error? Pinmembermax_j_liang5-Nov-10 9:36 
GeneralCollation Error but lovly article Pinmemberskashifz27-May-09 15:32 
GeneralRe: Collation Error but lovly article PinmemberKamal Singh Kharayat27-May-09 19:06 
GeneralRe: Collation Error but lovly article PinmemberKamal Singh Kharayat27-May-09 19:09 
GeneralRe: Collation Error but lovly article Pinmembervvr1514-Apr-10 20:13 
GeneralRe: Collation Error but lovly article PinmemberMember 80879446-Jul-12 12:21 
Generalgood one.. Pinmembermansuri.isteyaq9-Mar-09 19:49 
GeneralRe: good one.. PinmemberKamal Singh Kharayat9-Mar-09 20:07 
GeneralNice Article. But issue with Me. PinmemberAmitChampaneri15-Dec-08 19:36 
GeneralRe: Nice Article. But issue with Me. PinmemberKamal Singh Kharayat15-Dec-08 23:41 
GeneralRe: Nice Article. But issue with Me. PinmemberAmitChampaneri16-Dec-08 0:40 
GeneralRe: Nice Article. But issue with Me. PinmemberKamal Singh Kharayat16-Dec-08 1:29 
Generalnice artical Pinmembermhemal2-Sep-07 19:37 
GeneralEnable CLR PinmemberkurisutofuJP26-Aug-07 16:27 
QuestionError in naming? PinmemberkurisutofuJP26-Aug-07 16:22 
AnswerRe: Error in naming? PinmemberKamal Singh D. Kharayat26-Aug-07 19:24 
GeneralRe: Error in naming? PinmemberkurisutofuJP26-Aug-07 20:03 
GeneralThanx!! Had not known this functionality of SQL server... Pinmembernishantsagar8317-Aug-07 23:32 
QuestionInteresting article but a few questions PinmemberJon Masters15-Aug-07 0:08 
AnswerRe: Interesting article but a few questions PinmemberKamal Singh D. Kharayat15-Aug-07 21:29 
GeneralRe: Interesting article but a few questions PinmemberJon Masters16-Aug-07 0:01 
GeneralRe: Interesting article but a few questions PinmemberKamal Singh D. Kharayat16-Aug-07 0:43 
GeneralRe: Interesting article but a few questions PinmemberJon Masters16-Aug-07 1:08 
GeneralExcellent!!!!!!!!!!!!!!! PinmemberRashmi Patel RJ14-Aug-07 4:06 
GeneralVery Help Full Pinmembersneharahul14-Aug-07 2:55 
GeneralInteresting Pinmemberlallous13-Aug-07 22:37 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web04 | 2.8.150327.1 | Last Updated 27 Aug 2007
Article Copyright 2007 by Kamal Singh Kharayat
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid