Re: Multiple concurrent isolated transactions on ADO Dataset

What database do you use? You describe scenario that is easily handled by
practically any database. You said that amount of data is huge - creating
per-user copies will kill your server - think about memory allocation and
copying. Is it not possible to operate directly on database?

Peter

"Mark Roberts" <Mark_Roberts@xxxxxxxxxxxx> wrote in message
news:exDNqHvWFHA.612@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I have been thinking about a problem for some time, and i'd like to throw
> it open to the newsgroups in case someone has come across a similar
> situation.
>
> I have a C# .Net 2.0 web application with a very large server-side dataset
> (i.e. can only be 1 in memory).
>
> I have multiple users that wish to make changes to the dataset, and each
> user's should be batched up and only visible to themselves until they're
> committed, at which point they become part of the main dataset.
>
> I am thinking of have one dataset per user as well as the main dataset,
> and recording changes into the user-based dataset.
>
> This is ok, but it adds a lot of complexity when querying the data, since
> queries are essentially across two datasets.
>
> Ideally, i'd like to have multiple transaction layers on the main dataset,
> one for each user that isolates their changes, but permits dataset
> searching to work in the context of their transaction until it's committed
> or rolled back.
>
>
> Many thanks!
> Mark.
>


.

Relevant Pages