I have a really large stored procedure which calls other stored procedures and applies the results into temp tables.
I am debugging in SQL 2008 Management Studio and
Use global temporary tables, i.e. with double hash.
insert into ##temp select ...
While debugging, you can pause the SP at some point, and in another query window, the ## table is available for querying.
select * from ##temp
Single hash tables (#tmp) is session specific and is only visible from the session.
simply dont drop temp table or close transaction
eg
select * into #temp from myTable
select * from #temp
an alternative would be to use a variable in your stored proc that allows for debug on the fly.
i use a variable called @debug_out (BIT).
works something like this
ALTER PROCEDURE [dbo].[usp_someProc]
@some_Var VARCHAR(15) = 'AUTO',
@debug_Out BIT = 0
BEGIN
IF @debug_Out = 1
BEGIN
PRINT('THIS IS MY TABLE');
SELECT * FROM dbo.myTable;
END ................
END
the great thing about doing this is when your code launches your stored procedure, the default is to show none of these debug sections. when you want to debug, you just pass in your debug variable.
EXEC usp_someProc @debug_Out = 1
I built a procedure which will display the content of a temp table from another database connection. (which is not possible with normal queries). Note that it uses DBCC PAGE & the default trace to access the data so only use it for debugging purposes.