Niels SQL Server Blog - All Comments

Training Day 5 | Monir Blog

Training Day 5 | Monir Blog — Sat, 19 Nov 2011 14:03:39 GMT

Pingback from Training Day 5 | Monir Blog

Nestor Sulikowski » Debugging SQLCLR

Nestor Sulikowski » Debugging SQLCLR — Thu, 28 May 2009 20:58:46 GMT

Pingback from Nestor Sulikowski » Debugging SQLCLR

New SQLCLRPROJECT Released! | Programmer's Edge

New SQLCLRPROJECT Released! | Programmer's Edge — Sat, 27 Sep 2008 22:23:13 GMT

Pingback from New SQLCLRPROJECT Released! | Programmer's Edge

re: SQL Server 2008 February CTP Available

sentral — Tue, 15 Jul 2008 12:49:32 GMT

hi there,

does anyone know what license model should be used for 100s of users to access sql?

re: Service Broker over Remote Instances

Hai Tran Xuan — Fri, 14 Mar 2008 02:23:09 GMT

Service Broker Remote

re: GUI for Sql Server Service Broker

Kevin — Tue, 19 Feb 2008 17:58:08 GMT

I am glad someone is trying, but damn it is buggy. I wish MS would get off their a**es and make one integrated in to the management studio. Are you going to post this on source forge so we can have our bug fixes in for everyone?

re: SqlDependency

Nitin — Wed, 30 Jan 2008 03:31:47 GMT

Gr8 work. Thanx

re: SQL Server 2005 Debugging

John D — Thu, 24 Jan 2008 16:04:31 GMT

Probably a stupid question, but when you are doing simple Server Explorer debugging - that is, just debugging a stored procedure w/o CLR code - how do you see the values of temporary tables - or any table for that matter? Tooltips and Watches show the value of scalar variables (@varx, etx),, but where do you enter (while you are at a breakpoint) "SELECT * FROM #TempTable" or something similar? I've tried the immediate window, but it always says {expression} could not be evaluated.

re: Like Phoenix Rising ... or New Version of SQLCLRProjct

nielsb — Tue, 15 Jan 2008 12:00:34 GMT

Hi Simon!

I assume that when you say "the code" you mean the source code? If so, default is not to deploy, but you can change the setting to deploy the source as well.

In addition you can choose to not deploy the assembly to the server at all, but just create deployment scripts for the assembly and the methods/UDT's/UDA's in the assembly.

Niels

re: Like Phoenix Rising ... or New Version of SQLCLRProjct

simonsabin — Tue, 15 Jan 2008 11:45:32 GMT

Excellent. Am I right in thinking that your version doesn't deploy the code to the server unlike Visual Studio