Not really... as previously pointed out, the execution plans are identical... and so are their execution times on a quiet non-networked server... here's my test results on a million row...

This will not find the tables affected by calls to other procs within the proc identified as @objname... but it may do what you ask... and, you get some column...

Does anyone have a Microsoft link or know the lookup in BOL that says that Temp Tables are logged (or not?).  I know there is a log file associated with TempDB...

A bit oversimplified on my part put if you have 4 working stored procedures, why not just use UNION ALL to convert it all to a single record set?

SELECT yada-yada

  ...

My appologies, Lorna... I did think you were being sarcastic... glad you figured it out and thank you for the courtesy you intended.  Ian is correct... we had no way...

It's a forum... not an instant help button.  Your impatience may have cost you a great answer from one the good folks on this forum... we all work regular jobs...

Both Temp Tables and Table Variables start out in memory and both spill into TempDB when they get big enough... there are many other differences, as well...

http://support.microsoft.com/default.aspx?scid=kb;en-us;305977&Product=sql2k

...draw your own...

Sure... no problem...

OSQL -SwSRVR01 -E -Q"set nocount on  select name from sysobjects" -n -h-1

Doh!  The simplest answer is usually the best and the most elusive... that'll sure do it, Tim!  Good thinkin'

Nice job Lowell,

Small correction, though... the switch to turn off the header and the dotted line is -h-1 and not just -h1.

Check the size of TempDB on both servers.

Thanks dee-oh-gee... little hint... document as you go and you'll never get behind.

Our DBA had a job to check for "orphaned" temp tables and delete them.

If you mean find the...