> No, because there usually is no inherent table sort order, unless you are
> using a clustered index. Even then, I don't believe there is any
> *guarantee* that the updates will happen in that order.
>
> You could, of course, use a cursor, retrieved in the order you want, then
> update the records one by one.
To answer my initial question myself:
- have two tables: work_in, work_result, where work_in has all the data,
work_result is empty
- create the triggers as described before,not on UPDATE of work but on INSERT
on work_result
- insert into work_result the rows taken from an SELECT-FROM-ORDER-BY
statement (use the host-language to alter the data as necessary before
inserting them in work_result)
To my astonishment, it seems that this method is even faster than a "global"
update of the data. I expected that N inserts take more time than an single
update of N rows - but first tests indicate completely different behaviour.
Thanks for your help!
Daniel
--
Dipl.-Math. (FH) Daniel Franke
Institut fuer Medizinische Biometrie und Statistik
Medizinische Universit�t zu Luebeck
Ratzeburger Allee 160, Haus 4
23538 Luebeck
Telefon: 0451-500-2786
Telefax: 0451-500-2999
[EMAIL PROTECTED]
