Re: ADO Classic Scalability in Web Service
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Tue, 26 Feb 2008 16:40:36 -0500
randy collins wrote:
I have a legacy VB6 middle tier component that makes numerous database
queries and, ultimately, a DB insert via ADO, and I am very concerned
about scalability. I need to reuse this component in an ASP.NET web
service. This web service will be handling requests for numerous
clients, which will result in ADO queries and inserts across many
different databases. We expect this web service to ultimately handle
several transactions per second. Will the fact that we'll be hitting
perhaps 50 different databases from this one app render connection
pooling ineffective? Is "ADO classic" connection pooling even
initiated when running inside an ASP.NET process?
I don't know, but I don't see why it wouldn't be. You might try this
question in one of the dotnet groups.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
.
- References:
- ADO Classic Scalability in Web Service
- From: randy collins
- ADO Classic Scalability in Web Service
- Prev by Date: Re: Begin Tran open disconnected recordset - reconnect - rollback/comm
- Next by Date: Re: Begin Tran open disconnected recordset - reconnect - rollback/
- Previous by thread: ADO Classic Scalability in Web Service
- Next by thread: ADO/C++/EXCEL
- Index(es):
Relevant Pages
|
|
