"Warren Patterson" <des@newsgroups.nospam> wrote in message
news:uab8DFGsEHA.644@tk2msftngp13.phx.gbl...
> Can you use #temp tables in stored procedures that access data for a
> website?

> Will this not cause a slowdown if say 5 users of the website access the
same
> Stored Procedure at the same time? As far as I can tell if I use a
> statement like this "select * into #temp from tblOrders" a problem will
> occur as you cant have 5 #temp tables at the same time. Is this true? Or
> will Sql handle this?

"Steve Thompson" <stevethompson@nomail.please> wrote in message
news:O8c3VNGsEHA.2904@TK2MSFTNGP15.phx.gbl...
> "Warren Patterson" <des@newsgroups.nospam> wrote in message
> news:uab8DFGsEHA.644@tk2msftngp13.phx.gbl...
> > Can you use #temp tables in stored procedures that access data for a
> > website?
>
> Sure.
>
> > Will this not cause a slowdown if say 5 users of the website access the
> same
> > Stored Procedure at the same time? As far as I can tell if I use a
> > statement like this "select * into #temp from tblOrders" a problem will
> > occur as you cant have 5 #temp tables at the same time. Is this true?
Or
> > will Sql handle this?
>
> You would be creating Local Temporary tables, which are session based and
> should not conflict with any other local temporary table in use. Slowdowns
> are more subjective and dependent on your database design, and data access
> methodology. SQL Server can easily handle multiple temporary tables.
>
> Steve
>
>