Posted by Jeff Kish on 02/07/07 23:02

On Fri, 2 Feb 2007 10:18:24 +0000 (UTC), Erland Sommarskog
<esquel@sommarskog.se> wrote:

>Jeff Kish (kishjjrjj@charter.net) writes:
>> I am under the understanding that having the sql server 2005 db is not
>> enough (like 2000 was) to debug stored procedures.. that I need to
>> purchase (costly) visual studio 2005.
>>
>> Can someone suggest a free or lower cost alternative?
>>
>> sorry to be so cheap.. its the times I think.
>
>PRINT and SELECT is what I use, even in SQL 2000. I used to use the
>T-SQL debugger occasionally, but I gave up on it. There were so many stars
>that had to be aligned for it to work.
Thanks. I'll give it a try.
The debugger had been fairly nice to use when I had triggers and sp's
to debug.

I assume that it is a simple matter to invoke the procedure (I know
how to compile it) to get things to run?

Regards,
Jeff

• Next in forum: Re: I don't understand this "server timeout"
• Prev in forum: Re: I don't understand this "server timeout"
• Thread view: Re: any way to debug stored procedures without buying visual studio?

[Reply to this message]