FIMS Maintenance: DB health check

Currently when you run the DB health checks and see too many areas and blocks to extend or multiple lines in different areas when have to call in for reindexing; is there a way to automate this? It would be a huge time saver to have an subprogram monitor the database and when it reaches a treshhold run automatically to add additional indexes to the database in the background.                              Impact: Currently, I run the DB health check and usually about a week after I've had it re-indexed, it starts to show areas and blocks to extend, when it starts to encompass more that on area I call in for re-indexing: Here is a samples: c:\npo\found\dbfiles\found_7.d3 7 10,240 c:\npo\found\dbfiles\found_8.d3 8 12,480 Roni Olson
  • Guest
  • Aug 11 2015
  • Reviewed: Voting Open
  • Attach files
  • Guest commented
    September 18, 2015 13:28

    The DB Health Check indicates a need for storage to be added to the database. In order to add storage space, the database has to be taken offline, so it can't be something that happens automatically, like re-indexing which is about a continual optimization.

     

    I created a utility I use at my foundation that automates most of the process. It gives me a window where I type in a percentage for the areas and builds all the files necessary including a batch command to do the full rebuild of the database that I execute when I can bring the database down.

     

    If you want, I'm happy to share the utility with you or anyone else that would like it.

  • +50