InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 06:07:05 GMT20http://www.sqlservercentral.com/Forums/Topic764373-338-1.aspxGood luck, blue. It's really not difficult, just tedious and time consuming.Tue, 04 Aug 2009 07:24:15 GMTThe Dixie Flatlinehttp://www.sqlservercentral.com/Forums/Topic764373-338-1.aspxThank you all for responding. Yes, DCPeterson, creating that many temp tables is what I was afraid of. I will look into Matt's suggestion, but I'm not sure it would be any easier.And Quickly Confused is right, there is no auto way to do thissince none of the stored procedure output have the common columns.This is what I needed to hear before I proceed. thanks a bunch.Mon, 03 Aug 2009 20:46:27 GMTsqlbluehttp://www.sqlservercentral.com/Forums/Topic764373-338-1.aspxAre all the columns in common between the 50 stored procedures? Even if you defined a temp table with enough columns to handle any of the stored procedures, you would still have to define which columns are going to be populated by the output of the stored procedures. For examplecreate table #temp (many many columns)insert into #temp (colA,colB,colC)exec stproc1insert into #temp (colA,colC,colD,colE)exec stproc2insert into #temp (colA,colB,col,C,colD,colE,colF,colG...)exec stproc99There just isn't an "automatic" way to avoid all this with stored procedures. Mon, 03 Aug 2009 19:32:29 GMTThe Dixie Flatlinehttp://www.sqlservercentral.com/Forums/Topic764373-338-1.aspxWell - temp tables are certainly one way... but they're not the ONLY way. depending on what you want to do with them, you can set up a "self-linked server" and then use them a bit like table-valued functions and access their output as a table variable.As in - something like[code="sql"]Select * from openquery(MyLocalServer, 'exec mydbo.dbo.myStoredProc @Param=1')[/code]Mon, 03 Aug 2009 16:01:45 GMTMatt Miller (#4)http://www.sqlservercentral.com/Forums/Topic764373-338-1.aspxSorry to tell you this, but I think you are in for creating a bunch of temp tables. You can't execute a stored procedure from within a function or a select statement so that rules out being able to use the SELECT...INTO syntax and other than that the table that you are inserting into must already exist.However, if the stored procs don't have any parameters, why don't you define views and use those? A procedure with no parameters and that simply returns a result set is pretty much a view...Mon, 03 Aug 2009 15:07:17 GMTDCPetersonhttp://www.sqlservercentral.com/Forums/Topic764373-338-1.aspxI need to get the output from the stored procedures (50 of them), and insert into a temp table at each execution of a stored procedure. Is there a way for me to do this WITHOUT having to pre-define the temp table (because the columns are all different for each stored procedureoutput, otherwise I would have to create 50 temp tables, which I prefer not having to do it like that). I am not allowed to change the stored procedures. The stored procedures do not have any parameters, so I cannot use OUTPUT. if I have to create that many temp tables, then I guess I would have to, but I just wanted to make sure there is no other better option. any help/advice would be greatly appreciated.Mon, 03 Aug 2009 14:13:52 GMTsqlblue