#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Database physical file size compaction without changing DBID of the database.

This will help the incremental backup tools with other hand support to reduce disk space.

  • Guest
  • Jul 31 2020
  • No Plans to Implement
  • Attach files
  • Admin
    Thomas Hampel commented
    31 Jul, 2020 03:13pm

    I dont understand the problem.
    Running compact -c will change the DBIID on purpose to indicate that a fullbackup of the database is required. Without it you can not apply translogs anymore.

    Furthermore please note that you should not run compact over and over again to squeeze the size of the database to its absolute minimum because this will increase the fragmentation on disk. This can lead to performance problems. It is perfectly fine to keep some whitespace within the NSF, so that new documents will be writen into the whitespace rather than expanding the file on disk. Reorganizing whitespace (without reducing the NSF file size on disk) is the better choice.