Re: ADO - Bad when it is time to Optimize
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Sun, 11 Mar 2007 09:21:01 -0600
"Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx> wrote in message
news:eHjwxR9YHHA.3824@xxxxxxxxxxxxxxxxxxxxxxx
cvsudheer@xxxxxxxxx wrote:If
Is it even possible to create a disconnected recordset from a server-side<snipped>
cursor? I seem to recall attempting to do this once and getting an error.
I have a chance later today I will see if my memory is playing tricks onme.
Now you got me thinking, and I intend to go play myself later on. The
situation I remember was where code had been reworked to use a disconnected
recordset. They were using ADO 2.5 and the MSOracle provider (and Oracle
7???). There was no error - the disconnect just didn't happen.
ActiveConnection was 'nothing', but the connection was still out there.
Which leads to another interesting point. After rereading all the articles
you cited I was reminded of how many actors are actually involved in any
scenario - the data access version, the provider/driver (vendor), the
database version, and ultimately the wire. Something benign in one may have
profound effects in another.
Then you can have a situation where the engine/provider are spawning their
own 'extra' connections to support some kinds of queries. Quite beyond the
control of one's ADO calls or one's knowledge.
Which leads back to the OP's question - what is a good general tool or
method to use when trying to investigate possible pooling issues?
I started to offer some suggestions and then realized that I usually just
end up hacking my way through one damn scenario after another using "All of
the above" at some point or another. <g>
-ralph
.
- References:
- ADO - Bad when it is time to Optimize
- From: cvsudheer
- Re: ADO - Bad when it is time to Optimize
- From: Bob Barrows [MVP]
- Re: ADO - Bad when it is time to Optimize
- From: cvsudheer
- Re: ADO - Bad when it is time to Optimize
- From: Stephen Howe
- Re: ADO - Bad when it is time to Optimize
- From: Ralph
- Re: ADO - Bad when it is time to Optimize
- From: cvsudheer
- Re: ADO - Bad when it is time to Optimize
- From: Bob Barrows [MVP]
- ADO - Bad when it is time to Optimize
- Prev by Date: Re: ADO - Bad when it is time to Optimize
- Next by Date: Re: ADO - Bad when it is time to Optimize
- Previous by thread: Re: ADO - Bad when it is time to Optimize
- Next by thread: Re: ADO - Bad when it is time to Optimize
- Index(es):
Relevant Pages
|
|