Hi folks,

I had a question in comparing ADO to ADO .net, specifically on the
performance side. Here is some background:

Our application is a very data intensive one, we have a middle tier,
which is our database interface client, which talks to many SQL Server
databases. In programming this database interface client, we are
trying to figure out if we should do it in C++ (unmanaged) or c#
(managed), specifically, if we use c++ we will have to use ADO, and if
we use c#, we have to ADO .Net. The deciding factor will be which is
faster talking to (querying, updating, running stored procedures) to a
SQL Server box.

Does anyone have any thoughts on perf differences of ADO (in c++)
versus ADO .Net (in managed C#) ? Our primary factor for picking ADO
or ADO .net is perf, does anyone have any comparative perf numbers?

There are plenty of articles that talk about the differences between
ADO and ADO .net, but none i could find talk about perf. Anyone know?

Thanks,

Raman

I've written a chapter or two on this issue and it boils down to this:
It does not make a snit of difference which language you use to execute
the query or fetch the rows.

C++, VB3, VB.NET, MASM and C# all wait at the same speed. In my experience,
data access application performance has more to do with database and
application design and architecture than with how fast you generate and
submit the queries. You can gain far more performance by fetching fewer
rows, making fewer round trips, and executing SPs with a well-tuned query
plan than you can by switching from C# to C++ or FORTRAN. Yes, if you use
COM-based ADO "classic", there is a COM interop layer added around the ADO
code that slows down the operations, but not by much. Native interfaces like
SqlClient are far faster (and simpler) than the bloated OLE DB "OSFA"
interfaces, but these differences won't matter if your database does not
have an appropriate set of indexes or you have a print server on the same
system as the SQL Server.

hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi folks,
>
> I had a question in comparing ADO to ADO .net, specifically on the
> performance side. Here is some background:
>
> Our application is a very data intensive one, we have a middle tier,
> which is our database interface client, which talks to many SQL Server
> databases. In programming this database interface client, we are
> trying to figure out if we should do it in C++ (unmanaged) or c#
> (managed), specifically, if we use c++ we will have to use ADO, and if
> we use c#, we have to ADO .Net. The deciding factor will be which is
> faster talking to (querying, updating, running stored procedures) to a
> SQL Server box.
>
> Does anyone have any thoughts on perf differences of ADO (in c++)
> versus ADO .Net (in managed C#) ? Our primary factor for picking ADO
> or ADO .net is perf, does anyone have any comparative perf numbers?
>
> There are plenty of articles that talk about the differences between
> ADO and ADO .net, but none i could find talk about perf. Anyone know?
>
> Thanks,
>
> Raman
>