Den 2014-02-24 22:02 skrev Fabiano - Desenvolvimento SCI såhär:

>
> The right thing to do to avoid this kind of corruption is make diary
> backups and ensure you can restore them!
>
> If you can’t backup or not restore the entire database (including
> reactivating all foreign keys) you must stop immediately and try to
> fix the database.
>
> I think you ran this database corrupted for a long time or without a
> backup/restore for a long time.
>
> Fabiano.
>

Well, I usually run a full file copy using NBackup lock/unlock each
night, and also a full gbak each weekend to ensure that the DB is OK. I
also use a copy of the last NBackup copy as a test database for test &
development, which essentially means I now the copy works. This time
however, I had some "disturbances", so the last copy was a few days old,
which means I'd rather pay for help to get it fixed that revert to the
backup. Also, the gbak run was missing for the last two weekends. The
corruption has probably been present for about 2 weeks.

In the long run, I intend to switch to a more powerful server so that I
can run more regular backups and keep a longer backlog of backups
without various kinds of performance problems...

Thanks all the same!
Kjell