Re: Connections not closing
From: Jerry Pisk (jerryiii_at_hotmail.com)
Date: 03/26/04
- Next message: Vivek Hegde: "RE: ADOX"
- Previous message: Paul H.: "Connections not closing"
- In reply to: Paul H.: "Connections not closing"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 26 Mar 2004 00:00:43 -0800
Pretty much everybody else has, ADO has built-in connection pooling. By
default it keeps connections open for a minute after they're used. There are
connection string parameters you can use to change the pooling behavior.
Jerry
"Paul H." <anonymous@discussions.microsoft.com> wrote in message
news:F5AEE8CE-0688-4D00-B145-AC2F3426CFCC@microsoft.com...
> I'm using ADO 2.8 in a VB application and I connect to multiple databases
in a single instance of MSSQL. In my particular application I occasionally
want to close a connection so that I might re-attach an updated database or
restore the database from a backup (.bu) file. It appears that the
connection object has some form of persistence, because even though I close
the database I cannot perform some of the operations. Typically, the
operation will throw an error that indicates that the connection is still
active. I have a done a workaround, which essentially 'marks' the database
for this action. If my application is stopped and restarted, then before
any databases are opened, it performs the appropriate action on a 'marked'
database. This seems like a very circuitous workaround to get where I want
to go.
>
> Has anyone else experienced the persistent connection?
>
> Thanks in advance for your help.
- Next message: Vivek Hegde: "RE: ADOX"
- Previous message: Paul H.: "Connections not closing"
- In reply to: Paul H.: "Connections not closing"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
