Shulou(Shulou.com)06/02 Report--

This article mainly introduces how to use SQL SERVER CLR code debugging tools in Visual Studio. It has certain reference value. Interested friends can refer to it. I hope you will gain a lot after reading this article. Let Xiaobian take you to understand it together.

The benefit of developing SQL Server CLR code in Visual Studio is that you can take full advantage of debugging tools. We're pretty familiar with stepping through Visual Studio debuggers when developing plain. NET code, but how do we debug using Visual Studio when writing CLR code for SQL Server? Next, this article will introduce three debugging methods.

To better debug SQL Server CLR code, you need Visual Studio Professional or Team Edition. The following table lists the versions of Visual Studio and development languages in which you can use the debugger, as shown in Figure 1:

In addition to the correct version of Visual Studio and supported languages, you need to make sure CLR Integration is enabled in SQL Server. This can be set in SQL Server Peripheral Configuration. One particular caveat is that CLR debugging causes all other threads to stop, so never attempt to debug CLR on a production server. Once the data connection in Visual Studio Server Explorer (shown in Figure 2) is set to allow debugging, there is an additional item Server Explorer in the Visual Studio View menu item. Figure 2:

When you select Allow SQL/CLR debugging, you see the message prompt shown in Figure 3:

Once CLR is enabled in SQL Server and debugging is enabled in the connection entry, you can begin debugging. SQL SERVER CLR code debugging has three ways:

1. Step through SQL Server 2005 database objects using Server Explorer;

2. Use SQL Server projects in Visual Studio 2005 to run test scripts;

3. Run an application to invoke stored procedures.

Method 1: Step through an object

If CLR code has been deployed to SQL Server, we can browse CLR functions or stored procedures, right-click the object to debug, and select "Step Function" or "Step Stored Procedure" in the pop-up menu, as shown in Figure 4:

This operation will execute the function or stored procedure and a window will pop up where we can enter the values of the parameters, as shown in Figure 5:

After specifying the input values, press the OK key to begin the debugging process. First it stops at the beginning of the function code, whether we use breakpoints or not, as shown in Figure 6:

You can step through the code line by line using the function buttons on the debug control toolbar as shown in Figure 7.

In the local window we can see how the variable values change, as shown in Figure 8. In addition, we can also take advantage of other debugging functions.

Thank you for reading this article carefully, hope Xiaobian share "Visual Studio SQL SERVER CLR code debugging tool how to use" This article is helpful to everyone, but also hope that everyone more support, pay attention to the industry information channel, more relevant knowledge waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.