Re: Transactions in ADO.Net 2 strongly-typed datsets.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Gentlemen,

I would first like to thank you for your time and effort in helping me
and my team. After reading your latest comments today, we met and
decided on making some of your recommended changes to our approach.

Here's what we're doing:

We will still be using the strongly-typed datasets as a way to access
the data collections easily and to easily make insertions, updates and
deletes to the collection. However, when it's time to write the
dataset data to SQL, we will actually iterate through the rows and
(depending on row state) instantiate an our custom object, populate it
from the row data and then let the object add/update/delete item. This
limits object instantiation to only the items that were added or
changed in the dataset. This way, we also have very granular control
over the connection and transaction.

Also, one of the other requirements that wasn't in my previous posts
was that we will be keeping rather detailed change logs on most of our
data. Using a data adapter of any type made that requirement a bit
sticky. This new scenario makes that much easier.

Any thoughts?

Thanks,
Glen

.

Relevant Pages