ADO .NET right for raw data processing?

  • Thread starter Thread starter Tim
  • Start date Start date
T

Tim

Is ADO .NET performance adequate for processing large volumes of data?
For example, say you have a 500,000 customers with 700,000 orders a
month. You want to identify trends over one year, so you need to scan
over those 500,000 customers and 12 x 700,000 orders. During the
scan, you're checking each customer against 1000 different rules. If
you want to process 20 customers/sec, would ADO .NET be capable or
should this all be done in a stored procedure(s)?

Thanks in advance.

Tim
 
Stored procedures--no question. If the tests are complex, I might consider
calling an extended stored procedure. In the Yukon timeframe these can be
written in VB.NET or C# (and possibly other CLR languages).
Moving that volume of data to an application and back again is going to be
very expensive. Let the server crunch the data where it lives.
I would also consider reporting services to display the results...

--
____________________________________
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.
__________________________________
 
Tim,

It looks nice to me when the general manager in the US can see what where
the results with only one push on a button from the plant in China and/or
visa versa.

This goes very fast in my opinion when the SQL server is in the same
environment as the dotNet server or even faster when it is the same. However
not with a single stored procedure (which can be used by that by the way).

What I want to say with the text above, it depends on what is the enviroment
and for what/who it is needed.

Cor
 
I corrected again that much that the subject disapeared.

I was writting about a webservice.

Sorry,

Cor
 
Back
Top