debug a stored procedure in SQL Server 2005

Hi everyone!
How can I do to debug a Stored Procedure in SQL Server 2005 from SQL Server
Management Studio? I looked for the Debug... option when I right-clicked the
SP but it seems that in SQL Sever 2005 doesn't not exist.
Thanks.
Jaime LucciIt's not there; you'll have to use Visual Studio.
Adam Machanic
Pro SQL Server 2005, available now
http://www.apress.com/book/bookDisplay.html?bID=457
--
"Jaime Lucci" <jaimelucci@.hotmail.com> wrote in message
news:%23UcTRTc9FHA.1440@.TK2MSFTNGP12.phx.gbl...
> Hi everyone!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
> Server
> Management Studio? I looked for the Debug... option when I right-clicked
> the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
> Thanks.
> Jaime Lucci
>|||Hi Jamime,
Microsoft didn't migrate the TSQL debugger into Microsoft SQL Server 2005.
The only way to debug is to use MS VS 2005 Pro or Team Suite
http://www.sqlserver.org.au/blogs/u...go/default.aspx
kind regards
Greg O
--
Looking to use CLR in SQL 2005. Try some pre-build CLR Functions and SP
AGS SQL 2005 Utilities, over 20+ functions
http://www.ag-software.com/?tabid=38
"Jaime Lucci" <jaimelucci@.hotmail.com> wrote in message
news:%23UcTRTc9FHA.1440@.TK2MSFTNGP12.phx.gbl...
> Hi everyone!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
> Server
> Management Studio? I looked for the Debug... option when I right-clicked
> the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
> Thanks.
> Jaime Lucci
>|||On Wed, 30 Nov 2005 12:43:15 -0300, Jaime Lucci wrote:

>Hi everyone!
>How can I do to debug a Stored Procedure in SQL Server 2005 from SQL Server
>Management Studio? I looked for the Debug... option when I right-clicked th
e
>SP but it seems that in SQL Sever 2005 doesn't not exist.
>Thanks.
> Jaime Lucci
>
Hi Jaime,
The debugging function has been removed from SQL Server 2005. You'll
have to use MS Visual Studio.
If you (like me) want to see the T-SQL debugger return to SQL Server,
then vote for this suggestion at (warning, long URL may wrap):
http://lab.msdn.microsoft.com/Produ...BK411
74
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)|||On Thu, 01 Dec 2005 00:11:55 +0100, Hugo Kornelis
<hugo@.pe_NO_rFact.in_SPAM_fo> wrote:
>On Wed, 30 Nov 2005 12:43:15 -0300, Jaime Lucci wrote:
>
>Hi Jaime,
>The debugging function has been removed from SQL Server 2005. You'll
>have to use MS Visual Studio.
>If you (like me) want to see the T-SQL debugger return to SQL Server,
>then vote for this suggestion at (warning, long URL may wrap):
>[url]http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackId=FDBK41174[/url
]
Done!
Would you believe, there are places where SQLServer is used with
non-MS middleware and client technologies, from Powerbuilder to
(shudder!) Java and J2EE!? Not to mention stuff like Python ...
And worse yet, there are places where there are DBA and data architect
and similar jobs, that involve SQLServer and not (by default) Visual
Studio! Gasp! But I have been there, time and again!
J.|||!
> How can I do to debug a Stored Procedure in SQL Server 2005 from SQL
Server
> Management Studio? I looked for the Debug... option when I right-clicked
the
> SP but it seems that in SQL Sever 2005 doesn't not exist.
Does anyone know if the debugging interface is public? That way, we could
finally integrate a debugger in our database development tool :-)
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com|||On Wed, 30 Nov 2005 15:34:32 -0800, jxstern wrote:

>On Thu, 01 Dec 2005 00:11:55 +0100, Hugo Kornelis
><hugo@.pe_NO_rFact.in_SPAM_fo> wrote:
(snip)

>Done!
Hi J.
Thanks for your vote!
Current standing: 11 votes, average rating 4.91. That works out to 10
votes at rating 5, and one vote (mine <g> ) at rating 4.

>Would you believe, there are places where SQLServer is used with
>non-MS middleware and client technologies, from Powerbuilder to
>(shudder!) Java and J2EE!? Not to mention stuff like Python ...
>And worse yet, there are places where there are DBA and data architect
>and similar jobs, that involve SQLServer and not (by default) Visual
>Studio! Gasp! But I have been there, time and again!
Not to mention, places where the expense of acquiring MS Visual Studio
in addition to SQL Server is too high - none of the other features are
needed, and debugging alone isn't enough justification to splash out on
Visual Studio.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)