1. closing DB connection in ASP.NET does not close it per say.
We have a DB connection pooling. So when you close it you simply releasing it for grab. And next DB request to open connection will grab already opened connection. Thus saving some time required to open DB connection.
You got to remmeber that if you are using TEMP tables in MSSQL
2. Connection per say does not lock tables. Only SQL statements do when they run as batch. I am positive that it's something else that locking your table.
George.
"Nestor" <te**@test.com> wrote in message news:uR**************@tk2msftngp13.phx.gbl...
thats my question.. how come it's still locked?
"Scott Allen" <sc***@nospam.odetocode.com> wrote in message
news:o6********************************@4ax.com...
How are you locking the table with a closed connection?
--
Scott
http://www.OdeToCode.com/blogs/scott/
On Sat, 30 Jul 2005 18:18:45 +0800, "Nestor" <te**@test.com> wrote:
I'm writing a simple aspx page that allows users to key in some data and
submit them into a SQL2k database. I realised that even after that db
connection closes and the page unloaded and closed, the table will still
belocked in the database. Is there any way to unlock the table after the
process is completed?
Thanks in advance