Re: DAO > SQL Server Processes
- From: Trevor Best <nospam@xxxxxxxxxxxxxxxxx>
- Date: Tue, 25 Oct 2005 11:27:03 +0100
Erland Sommarskog wrote:
Do DAO have connection pooling? Modern client libraries have connection pooling, which means that when you close a connection from the code, the API lingers on the connection for a minute, in case you would reconnect directly. In such case, it's perfectly normal to see the connections around.
Else, the only reason I can think of is that you had a transaction in
progress when you closed the connections, and the rollback takes a long time. If you vie the processes with sp_who what state and active
command do they have?
I've seen this in Access and it's a PITA as it makes changing users impossible without restarting it, e.g. log in as "sa" then close everything and log in as "joe", the front end thinks you are "joe" but the back end thinks you are "sa", which can cause unpredictable results.
If it's connection pooling in place then I don't think it was implemented right. I've seen it work the other way as well while logged in as normal user I then try to log in as "sa" to manage users, etc and get told I have no permission to do it.
.
- References:
- DAO > SQL Server Processes
- From: Chris
- Re: DAO > SQL Server Processes
- From: Erland Sommarskog
- DAO > SQL Server Processes
- Prev by Date: Re: too many connections
- Next by Date: Record , Row number
- Previous by thread: Re: DAO > SQL Server Processes
- Next by thread: Create Procedure Output ntext
- Index(es):
Relevant Pages
|
