Re: Temporary results used by SP
From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 01/04/05
- Next message: Uri Dimant: "Re: connect to sql server"
- Previous message: Uri Dimant: "Re: SUM and MAX"
- In reply to: FGItaly: "Temporary results used by SP"
- Next in thread: FGItaly: "Re: Temporary results used by SP"
- Reply: FGItaly: "Re: Temporary results used by SP"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 4 Jan 2005 13:34:57 +0100
You can create the temp table prior to the execution of the stored procedure and have the sp insert
etc the data in it and then use the data after the execution of the procedure.
-- Tibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ http://www.sqlug.se/ "FGItaly" <FGItaly@discussions.microsoft.com> wrote in message news:4CA935A9-232F-49BD-8C8F-76FE49F24B3B@microsoft.com... > In a MS Access Application you can use the "link table" to connect to a > common mdb file for the main database and a local mdb file for temp > tables/results. > > How to reproduce this scenario in Sql Server ? > From VB.NET these are the steps I would like to perform: > a) call a SP to do the heavy works, querying multiple tables and fill the > result table "xyz" > b) use the data in "xyz" to do something > c) drop the "xyz" table > > I can't use #temp tables cause they will be dropped at the end of the SP. If > I use a permanent table, what about if two or more users do the same > operation ? And what about performance ? > >
- Next message: Uri Dimant: "Re: connect to sql server"
- Previous message: Uri Dimant: "Re: SUM and MAX"
- In reply to: FGItaly: "Temporary results used by SP"
- Next in thread: FGItaly: "Re: Temporary results used by SP"
- Reply: FGItaly: "Re: Temporary results used by SP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|