Richard,
Yes, I've changed it use TRUNCATE rather than DELETE and it's working
well for us now.
The switching of the database is a good idea - thanks. Unfortunately,
we've not got enough disk space currently to do that, but if we get
problems in the future that will definitely be something we'll consider.
Rob
Richard Huxton wrote:
> Rob Kirkbride wrote:
>
>> I've introduced a --delete-not-drop option which simply does a DELETE FROM %
>> rather than 'DROP and then CREATE'.
>>
>
> Beware foreign-keys slowing you - TRUNCATE all relevant tables should be
> the fastest method if possible.
>
>
>> I hope this sounds sensible and I haven't missed something - I'm still
>> learning!
>>
>
> Have you considered restoring to a completely different database
> (report1/report2) and just switching between them?
>
>