About the size warning levels

Specify the percentage of database capacity as the
Warning level
 or
Critical level
. The status of database usage appears in the status bar of the FactoryTalk AssetCentre desktop client.
  • If the used space of database is greater than the Warning level and below or equal to the Critical level
    :
    The database usage status appears yellow.
  • If the used space of database is greater than the Critical level
    :
    The database usage status appears red.
When the database capacity reaches the warning or critical level, a warning message appears when you run the FactoryTalk AssetCentre desktop client, indicating the database usage status.
When the used space of database exceeds the
Critical level
, the following operations are affected:
  • New assets
    Cannot add new assets.
  • New file versions
    Cannot check in new file versions manually.
  • Event, Audit, and Diagnostic and Health logs
    Continue to write Event, Audit and Diagnostic and Health logs.
    If Event, Audit, and Diagnostic and Health logs do not exceed their maximum size, FactoryTalk AssetCentre generates two new logs:
    - The first new log is the Event, Audit, or Diagnostic and Health log.
    - The second new log is a warning log about the current AssetCentre database size exceeding the default threshold. The warning log includes the current database size status information.
    If Event, Audit, and Diagnostic and Health logs exceed their maximum size, FactoryTalk AssetCentre generates three new logs:
    - The first new log is the Event, Audit, or Diagnostic and Health log.
    - The second new log is a warning log about the current log type exceeding its maximum size. The warning log includes the current log size status information.
    - The third new log is a warning log about the current AssetCentre database size exceeding the default threshold. The warning log includes the current database size status information.
  • Backup, Backup and Compare, and Change Detect schedules
    Cannot create Backup, Backup and Compare, Change Detect schedules, or check a new version into the archive after schedules complete.
    Can edit Backup, Backup and Compare, and Change Detect schedules, and the schedules can continue to run.
    The new log message for these schedules behaves the same as the above Event, Audit, and Diagnostic and Health logs.
  • Search schedules
    Cannot create Search schedules.
    Can edit search schedules, and the schedules can continue to run.
    The new log message for search schedules behaves the same as the above Event, Audit, and Diagnostic and Health logs.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal