Hi.
Stats D7
       v 4.24
       C/S application

I’m enhancing an application that updates several files with data in
“Batch mode”.  This will now be done during working hours.  Prior to
this all “Batch mode” updates were processed overnight. I’m updating the
target tables with straight file processing.

Currently:
The users have only read capabilities on the data.
The data is served to them via SQL statements.

Because of this “live” data update, I’m concerned that the process will
crash if I send in a record that is currently in use.  BTW, I have to
replace any existing records with a new record. That is deleting all
detail records and adding new ones.

So what would be the safest solution for this?

I was thinking that I set the “request live” to false on the above SQL
statements?  That’s all I got!

Allan

Allan


Go for transactions and keep the batch sizes as small as possible so that it doesn't take to long.

Roy Lambert

Roy Lambert wrote:
> Allan
>
>
> Go for transactions and keep the batch sizes as small as possible so that it doesn't take to long.
>
> Roy Lambert
>
Roy; Hi and Thanks. I'll do the research and use your suggestion.

Allan

Allan,

Roy is correct - use small batches of transactions and just update the
tables in-place.  Because the users can't even edit records, then there
won't be any record lock conflicts to deal with.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:
> Allan,
>
> Roy is correct - use small batches of transactions and just update the
> tables in-place.  Because the users can't even edit records, then there
> won't be any record lock conflicts to deal with.
>
Thanks again Tim and Roy. The record-locking was the rub on this one

Allan