Dataset and scalability issue

[Nick nkw]

I am creating a winforms application. Drag and drop and VS 2005
automatically created Dataset based on the MDB schema. I found it seems
that all the changes are cached in the memory. Will the default way has
any scalability issue if the database tables are huge? What's the
solution if it does have the issue?

 

[msgroup]

Hi, Nick:

You may need to read the short article at
http://www.udaparts.com/devguide.htm for limitations of current version of
ADO.NET

In short, you can NOT depend on ADO.NET for high performance desktop and
middle tier applications. See the above article.

Regards,

 

[William \(Bill\) Vaughn]

One of the problems with the DataTable object is its name. While it can
contain all of the rows a database table, it's (insert expletive) to do so.
As I discuss at length in the book, a DataTable should contain a logical
subset of the rows you need at the time. Any operations that need to be
taken against the entire table need to be done on the server--not in memory.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
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.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)

 

[Cor Ligthert [MVP]]

Bill

Any operations that need to be taken against the entire table need to be
done on the server--not in memory.

I think that better is to write next time, "-not at the client", both is of
course in memory

Cor