День добрый

Sybase ASE 12.5.1

раз в сутки делается бекап базы данных, перед бекапом делаю dbcc checkstorage.

Вопрос в общем то в следующем: база рабочая, тоесть данные туда заливаются довольно таки интенсивно и постоянно, dbcc выдает предупреждения на suspect condition. Что то типа того:


DBCC CHECKSTORAGE for database 'bill' sequence 195 completed at Feb 9 2005
4:05AM. 0 faults and 8 suspect conditions were located. 1 checks were aborted.
You should investigate the recorded faults, and plan a course of action that
will correct them.
Suspect conditions are to be treated as faults if the same suspect condition
persists in subsequent CHECKSTORAGE operations, or if they are also detected by
other DBCC functions.
Checking current database: Logical pagesize is 4096 bytes
The following segments have been defined for database 4 (database name bill).
virtual start addr size (logical pages) segments
-------------------- ---------------------- --------------------------
50331648 5120000
0
1
67108864 512000
2
DBCC execution completed. If DBCC printed error messages, contact a user with
System Administrator (SA) role.



sp_dbcc_recommendations говорит следующее:


========================================================================

Generating recommendations for database bill.
================================================================================

Database level recommendations:

Run dbcc checkalloc with the 'fix' option.

Reload the database from a clean backup.

================================================================================

Recommended corrective action for object syslogs, objid 8:

Run dbcc checktable.

Suggested corrective actions for object trafficAccountDetail, objid 1045575732,
listed in recommended order:

Run dbcc indexalloc with the 'fix' option.
Run dbcc tablealloc with the 'fix' option.
Drop the object and recreate it.

================================================================================


как поступать в таком случае ?

Вопрос возник потому что проверив чуть пожже опять БД предупреждения несколько другие.

Могут ли suspect condition возникать во время интенсивной работы БД ?