Re: Why all the connections?
- From: "Vitali Kalinin" <vitkalinin@xxxxxxxxx>
- Date: Mon, 30 Jan 2006 18:06:34 +0200
"Kevin Davidson" <kevin@xxxxxxxxx> ???????/???????? ? ???????? ?????????:
news:43de2912@xxxxxxxxxxxxxxxxxxxxxxxxx
> Vitali Kalinin wrote:
>> Which CursorLocation, CursorType and LockType do you use for the
>> datasets? ReadOnly, ForwardOnly, ServerSide cursors could result in
>> behavior that you had described.
>>
>>
>>
> Yes, I am using clUseServer, ctOpenForwardOnly and ltReadOnly. I would
> like to learn more about why this could cause multiple connections. I will
> try other combinations.
>
> I believe I have other applications with the same cursor and locking that
> do not exhibit extra connections. I need to do more study.
>
> Thanks (spacibo),
>
> Kevin
MS SQL OleDB allows only single open fire horse cursor per connection, but
ADO tries to hide that restriction from you and silently clones connection
busy with fire horse cursor. So you should always close fire horse cursors
ASAP. Also I would consider using SQLjoin instead of doing lookup for each
record on the client side.
Regards,
Vitali
.
- References:
- Why all the connections?
- From: Kevin Davidson
- Re: Why all the connections?
- From: Vitali Kalinin
- Re: Why all the connections?
- From: Kevin Davidson
- Why all the connections?
- Prev by Date: Re: Why all the connections?
- Next by Date: Re: SQL statement contain " character
- Previous by thread: Re: Why all the connections?
- Next by thread: Re: Why all the connections?
- Index(es):
Relevant Pages
|