The logging database has grown too big

Possible cause  

The size of the logging database can grow so much that it needs to be reduced in size.

Proposed action  

Choose one of the following alternatives to reduce the size of the logging database:

  • Decrease the archive and the purge time frame. Run the following command:

    Qlik.Logging.Service.exe update --archive_age 15 --purge_age 30.

  • Set the maximum database size. Run the following command:

    Qlik.Logging.Service.exe update --maximum_db_size_in_gb n.

    Where n is a positive integer.

    Note: If n is a value less than two (2), the enforcement functionality is disabled. If n is equal to or greater than two (2), the functionality is enabled, allowing the Logging service to delete entries from the database once the maximum size specified is exceeded. Please note that this process is inexact and therefore it is not possible for the Logging service to enforce the maximum database size precisely.
  • Manually purge the database.

  • Turn off database logging. Run the following command:

    Qlik.Logging.Service.exe update --database_logging off.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?