Erik wrote:

The stats job failed halfway through on the en: 'old' SQl dump. This happened before, since huge en: has been split into 2 files. Second part probably corrupt/incomplete.

Yikes! Do you mean to say that the script completely starts over for every update? Would it not be better for the script to know the last time and place in the 'old' dump it did its last update and only compute the data that has been added since that update?

-- Daniel Mayer (aka mav)