I had written a algorithm, that gets executed daily. it does the following.
Make use of 4 auxillary tables , A,B,C,D. Reads from the other database tables, using few rates and updates or populates ranks and order in A,B,C, D.
Once this is done, it enters a fixed iteration loop. It updates a table say, tabA every time it iterates. This table is critical and millions of records updation in each iteration and the useful stabilized data happens to be in the last iteration.
What wuold a expert do in this scenario? I am thinking of updating this main critical table with stabilized data and so prefers only repopulated in the final iteration.
Should i keep a auxillary table for this table as well?
Is there any good architecture or design flow that i could use to keep this table being acted upon on each iteration? I would like to have pointers or suggestion for furter readings and coming up myself with some nice understanding and better flow of process.
Thanks in advance ,
With regards,
HariSaff