In Solution Explorer, right-click the project, and select Add, New Item.

You can use the SQL LocalDB instance that comes with Visual Studio. Open Microsoft Visual Studio, and create a new SQL Server project. Use the following steps to debug a CLR database object in Microsoft Visual Studio: For more information about enabling TCP/IP protocol on the server, see Configure Client Protocols. The TCP/IP network protocol must be enabled on the SQL Server instance in order to use Visual Studio for remote development, debugging, and development. The interaction between a debugger and SQL Server happens through distributed Component Object Model (COM).įor more information and scenarios about debugging managed stored procedures, functions, triggers, user-defined types, and aggregates, see SQL Server CLR Integration Database Debugging in the Visual Studio documentation. Debugging supports all common debugging features within routines executing on the server. However, SQL Server does not allow debugging existing connections. Because the functionality of the debugger is not limited by the type of connection, both tabular data stream (TDS) and HTTP connections can be debugged. A debugger can detect and debug activities only to the client connection to which it is attached.

Overviewĭebugging in SQL Server follows a per-connection model. Although Transact-SQL debugging does not freeze other executions on the server, it could cause other connections to wait by holding a lock.Įxisting connections cannot be debugged, only new connections, as SQL Server requires information about the client and debugger environment before the connection can be made.ĭue to the above restrictions, we recommend that Transact-SQL and CLR code be debugged on a test server, and not on a production server. However, you can continue debugging Transact-SQL in other connections.

This limitation applies because all CLR code execution freezes when a break point is hit and execution does not continue until the debugger advances from the break point. The following restrictions apply while debugging:ĭebugging CLR routines is restricted to one debugger instance at a time. Debugging permissions and restrictionsĭebugging is a highly privileged operation, and therefore only members of the sysadmin fixed server role are allowed to do so in SQL Server. NET Framework pre-installed, and Visual Studio.

NET 2003 cannot be used for CLR integration programming or debugging.

Clr browser source plugin 2016