Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

I have a stored procedure I need to call several different times passing in different paramaters each time. I would like to collect the results as a single dataset. Is something like this possible ...

exec MyStoredProcedure 1
UNION
exec MyStoredProcedure 2
UNION
exec MyStoredProcedure 3
I tried using the syntax above but got the error ...
Incorrect syntax near the keyword 'UNION'
The stored procedures I am dealing with are pretty complex and sort of a "black box" to me, so I cannot get into the definition of the stored procedure and change anything. Any suggestions on how to gather the results together?
I am using SQL Server 2008 R2. Thanks for any help.
You'd have to use a temp table like this. UNION is for SELECTs, not stored procs
CREATE TABLE #foo (bar int ...)
INSERT #foo
exec MyStoredProcedure 1
INSERT #foo
exec MyStoredProcedure 2
INSERT #foo
exec MyStoredProcedure 3
And hope the stored procs don't have INSERT..EXEC.. already which can not be nested. Or multiple resultsets. Or several other breaking constructs
                Thanks for the example. Should I explicitly DROP the temp table or does SQL Server take care of dropping it itself?
– webworm
                Mar 13, 2011 at 20:33
                It will be dropped when connection is closed, or when no longer in scope (say this code above is itself a stored proc)
– gbn
                Mar 13, 2011 at 20:42
                for more robustness consider using table variables instead of # tables. declare @myRetTab table (somcolumn ...) 
– Ben
                Jan 17, 2012 at 12:28
                Ben, table variables are bad for query optimization, gbn.....ur answers are the best always
– Bill Blankenship
                Apr 12, 2013 at 21:50
You can do all of that but think about what you are asking......
You want to pass multiple parameters to the sp and have it produce the same format result set for the different params. So you are, in effect, making a loop and repeatedly calling the stored proc with scalar data.
What you should do is rewrite the sp so that it can take sets of parameters and provide you with a combined result. Then you only do 1 set based operation.
You can pass table variables into an sp in 2008 as long as you make your own type up first.
                The OP specifically says "The stored procedures I am dealing with are pretty complex and sort of a "black box" to me, so I cannot get into the definition of the stored procedure and change anything" this answer may be right but completely fails to acknowlege that part at all!
– Martin Smith
                Mar 14, 2011 at 13:02
                The OP described the stored procedures as black box. Rewriting the stored procedures is clearly not an option for the OP.
– WonderWorker
                Jul 21, 2015 at 10:42
Hello I had this same issue.
I found the solution here
If you need to so something like this (this will not work) :
exec test1 'Variable1', 'Variable2';
UNION
exec test2 'Variable1', 'Variable2;
How to do the union of the 2 store procedures:
Create a variable as table.
Define all the columns that will return the store procedure in the variables of the table.
Make the union of the variables.
--First variable
declare @table1 as table ( 
    column1 nvarchar(20) ,   
    column2 nvarchar(30),
    column3 nvarchar(50)   )
--Second variable
  declare @table2 as table ( 
       column1 nvarchar(20) ,   
       column2 nvarchar(30),
       column3 nvarchar(50)  )Insert into @table1 
--Input the data returned from the store procedure into the variables
exec test1 'Variable1', 'Variable2';
Insert into @table2
exec test2 'Variable1', 'Variable2';
--Make the union with the variables
   select * from @table1 
    UNION 
   select * from @table2
I hope this post will help the next colleagues that will find this as an issue.
        
Thanks for contributing an answer to Stack Overflow!
Please be sure to answer the question. Provide details and share your research!
But avoid …
Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.