kkam, you are correct.  Hmmm - I thought I had done so before but obviously not... Perhaps I was using a UDF of some sort as the source.

In any case, you could still use a #temp table rather than a ##temp table.  The scope is limited to the DB connection rather than the current SQL block but it's still not global.

That would probably work.  However, I am not sure what happens if the SP were called again before the first call could finish executing.  This SP is called from a web page and my concern is that before the contents of the table could be cleared after we are done processing the request, the SP could be called again.

Is that a valid concern or am I off in my understanding of SP execution within SQL server?

Thanks again

The temporary tables prefixed with a single # are scoped within a single database connection.  Thus if you have 10 hits on your website then you might have 10 concurrent database connections (being simple here - no pooling or other voodoo ).  Each connection can have its own temp table.  Thus the use of temp tables within the stored proc should not cause any problem.

A global temporary table (prefix ##) IS shared - much like a standard fixed table in the database.

Thanks!  That narrows down the wires that were crossed for me.  I won't have a chance to test it for at least a few days but I'll keep you posted.

Thanks again!