Re: Best way to increase concurrency when using adopenstatic ?
- From: "Paul Baker" <paulb@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 27 Feb 2006 16:45:24 -0500
What type of lock does it supposedly hold? I don't understand how moving to
the last record will affect locks,
Do you have a reference to this article?
Paul
"Ian Ippolito" <IanIppolito@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F886A278-15C3-42FA-B084-7B6968750F78@xxxxxxxxxxxxxxxx
I am forced to use adOpenStatic cursors on a few queries on a high volume
website (over 10 million page views/month) running Server 2005 (64 bit
version).
I read an article about SQL Server 7.0 stating that when you open a static
cursor, SQL Server holds locks on the rows until you get to the very last
row. So it recommended that you do a .MoveLast and then .MoveFirst to
increase the concurrency.
Is this still a valid technique in sql server 2005?
Thanks,
.
- Prev by Date: Re: Automatically running an application every day
- Next by Date: Re: Best way to increase concurrency when using adopenstatic ?
- Previous by thread: Re: Inherit ado method
- Next by thread: Re: Best way to increase concurrency when using adopenstatic ?
- Index(es):
Relevant Pages
|
|