Note that the icon has a little lock on it and if you right click on the stored procedure, the ‘Modify…’ option is greyed out. If this step went according to plan, you should have an awesome new procedure listed under the ‘Stored Procedures’ folder of your database. CREATE PROCEDURE RunPerfLoadĪS EXTERNAL NAME.

We also don’t have any input or output parameters since this is just designed to create load on the system, but if you need input/output parameters, see the last section of this post. Unfortunately, the documentation on this isn’t as straightforward as it could be. Notice that when referencing the function, it’s specified as. That’s fairly straightforward and can be done with the little snippet of T-SQL that’s listed below. Now that we’ve successfully loaded the CLR assembly into our database, we need to create a procedure that will call into the assembly. How sweet is that? Pretty freaking sweet, I think! Create a procedure that calls into the CLR assembly After you’ve chosen the assembly, the ‘New Assembly’ window should look something like this:Ĭlick OK on the ‘New Assembly’ window and if all is well, the new assembly will be displayed under the ‘Assemblies’ folder of your database: In the window that opens, navigate to your newly created CLR assembly and select it. In the window that opens, choose the ‘Browse…’ button next to the ‘Path to assembly’:’ text box: From SQL Server Management Studio, expand the database name, then expand the ‘Programmability’ folder, then right click on the ‘Assemblies’ folder, and choose ‘New Assembly…’ like so: Once the assembly has been built in Visual Studio, it will output a. Now that we’ve built our CLR assembly, we need to load it into our SQL Server database. The code behind our assembly looks like this: public static void RunPerfLoad() We just need enough load to demonstrate the process. For the sake of the performance testing that I needed to accomplish, it didn’t need to be complicated, so neither will this version. The first step to running CLR code from SQL Server is to build a CLR assembly. It was a new experience for me, so I thought I’d share the details with you. It seemed to me that the first step to do that performance testing was to create a CLR assembly in SQL Server. Recently I had a need to do some performance testing against a CLR assembly in SQL Server.

Visual studio 2017 sql server clr