|
|
|
|
|
| | |
| |
Active Server Pages ASP ASP.NET .aspx .ascx Web HTML Developer Internet Microsoft Web Services Visual Studio .NET CJWSoft ASPProtect ASPBanner ASPClassifieds
(Advanced)
(Components)
(Database)
(General)
(Vbscript)
|
|
|
|
Subject: |
Re: connection pooling and #tables (temp tables) |
|
From: |
drdara |
|
Date: |
1/30/1999 2:16:41 PM |
|
IP: |
207.217.241.133 |
|
It is not possible for another connection to access someone elses temp tables when they are defined with a # sign in front of the name(it is private to that connection). If you want all connections to access the temp table then define it by using the ## in front of the name(global to all connection). The general purpose of ADO 2.0 connection pooling is to manange database connections and keep them alive if they are used often - it increases performance. Since a temp table is only private to the connection and many users are going thru the connection because of ADO 2.0 Connection Pooling, your #temp tables will not be private to that user. Dropping the table after you are done with it might help a little but not for sure becuase another user might try to use it thru the some connection before it was dropped by the first user on the connection. The solution might be, I say might because I have not tried it yet, to pass the users session.id to the sp that creates the temp table and use that session.id as the name of the temp table. |
Previous Message
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
