Re: ADO - Bad when it is time to Optimize
- From: "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom>
- Date: Sat, 10 Mar 2007 19:17:01 -0000
We have a situation where SQL server gets slow in processing requests
due to some contention issues and at that point I can see the User
Connections shooting up.
You ought to bear in mind that SQL Server is such that you can only have
_ONE_ active Server-sided, ForwardOnly cursor per-connection.
You cannot have 2 or more for the same connections. You can have multiple
types of other cursors. Just not 2 active Server-sided, ForwardOnly cursors.
It is a SQL Server limitation.
And I beleive, but not checked it out, that ADO will duplicate a connection
just to give you your 2nd Server-sided, ForwardOnly cursor.
I use Server-sided, ForwardOnly cursor a lot, but I tend to use them
serially so I dont run into this limitation.
Stephen Howe
.
- Follow-Ups:
- Re: ADO - Bad when it is time to Optimize
- From: Ralph
- Re: ADO - Bad when it is time to Optimize
- 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
- ADO - Bad when it is time to Optimize
- Prev by Date: Re: Public member not found
- 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
|
|