I think your missing the point Datasets are a cache when they are located in
a middle tier anything that hits them is going to be lighting quick . There
are 2 exceptions

1. Updates - Updates have to go to the DB and there is no batching with
datasets they go one at a time . If you are waiting on a lot of updates to
complete it will be a while before they come back. This is twices as bad as
to the DB  direct as you send it to the middle Tier who sends it to the DB 1
at a time.

2. Large DB's tables dont fit in a datset. Hence you have to partially cache
it and hancdle the cache miss. Using a DataREader here is about 2* as quick
as filling the dataset with the appropriate new rows and/or merging it back.

Ben

-----Original Message-----
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED]]On Behalf Of Thomas Tomiczek
Sent: Tuesday, 15 October 2002 10:25 PM
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] Learning to work with layers.


Dont worry. It is wrong.

Inline with ***

Thomas Tomiczek
THONA Consulting Ltd.
(Microsoft MVP C#/.NET)

-----Original Message-----
From: Franklin Gray [mailto:[EMAIL PROTECTED]]
Sent: Dienstag, 15. Oktober 2002 15:38
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] Learning to work with layers.


"The only thing so far is you look like using the standard .NET DB
access. These have slow updates." by Ben

Got a reference to this?

*** Update speed is not bad compared to the database speed (reads: not
too much overhead). Can it be that this is a DatSet with thousands of
rows and a FEW being updated? This would be understandable, then.


"In addition .NET select method are effecient only if you need to get
the data in big chunks preferably whole tables which means you will need
lots of memory." by Ben

How so?

*** Thats a good question. I have a lot of stuff here that makes a lot
of selects, and they run with good speed. Maybe a missing index or
something.

*** Definitly something I would love to see some proof for the
statement. Some numbers to see how bad you think this it. AND numbers
that compare the execution to the speed in lets say VB with ADO - just
to make sure that it is not your database that is slow.

*** Thomas

You can read messages from the Advanced DOTNET archive, unsubscribe from
Advanced DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced 
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to