ADO Classic Scalability in Web Service

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? Any insight into this
would be appreciated.
--
randy
.

Relevant Pages

  • Re: Why not use DAO?
    ... You have been refering to DAO vs. ADO when these two things (in the context ... you must have ALREADY used a provider to get to. ... interface for working with JET databases. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: The best elegant solution to override 65k rows limit in a sheet
    ... All math may reduce to arithmetic when calculating cardinal and ordinal ... The calculations take place in the same CPU for Excel and Access, ... The problem with databases is the relative inflexibility of tables as ... data structures and the awkwardness of queries as the only referencing ...
    (microsoft.public.excel)
  • Desperate for help on serious TCP/IP connectivity problem
    ... MSDE either SP2 or SP3a) via TCP/IP under ADO results in queries being ... the connection to the database is made via TCP/IP ... We suspect that deep in the TCP/IP stack something is pumping messages, ...
    (microsoft.public.sqlserver)
  • Re: Why not use DAO?
    ... Happy Christmas an fine holidays for you too. ... interface for working with JET databases. ... discussion about that (DAO was also faster as classic ADO) ... universal provider so ofcourse DAO wil outperform ADO in most ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... Don't listen to those who say something about your English. ... interface for working with JET databases. ... discussion about that (DAO was also faster as classic ADO) ... universal provider so ofcourse DAO wil outperform ADO in most ...
    (microsoft.public.dotnet.languages.vb)
Loading