September 8, 2006 at 12:09 pm
I had seen the:
CREATE TABLE #tmp (...)
INSERT #tmp (...)
EXEC @err = some_sp @par1, @par2 ...
approach for processing stored procedure result set but this method has a limitation when it is used by nested SPs.
I wish to know if there is another approach to solve this problem.
Regard,
john
September 8, 2006 at 5:06 pm
Create the temp table at a higher level in the nest. Or, use a global ##temp table (only one named instance can live at a time).
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2006 at 2:02 am
You can also use "Permanant" temp table thats build in your outer procedure and the inner procedure can populate/update it and the temp table isdeleted after its done using the results.
Thanks
Sreejith
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply