Hi.

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.

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.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

On Feb 2, 3:18 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> Jeff Kish (kishjj...@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.
>
> --
> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>
> Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
> Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

~
T-Sql debugger is some what okay, I used very long back.
I'm very comfortable with Print and Select commands to debug a stored
procedure.

~NR

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

Jeff Kish (kishjjrjj@charter.net) writes:
> 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?

Not sure that I understand the question, just run it from Query Analyzer.

Triggers are a good point for the debugger. If you are not aware of that
there is a trigger, the debugger can make you aware, if you stick to F11.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx