The Noah System database has a 4 GB size capacity. This database size is adequate for most Noah locations, but for larger locations and offices with many years of Noah data, the database may start to reach capacity.

After reaching 3 GB Noah will start showing a warning message ‘Database almost full’. This is a good time to start looking at next steps.

Database size can be seen in the Noah Console under Database Details. The numbers are displayed in MB rather than GB with the full capacity of the Noah database as the header and the used and free amounts below.

If the database is slow growing, you may have plenty of time before reaching 4GB. You can review options to reduce the size of the database and stay under the limit.

Or possibly it is inevitable that you will reach 4 GB and even more. In this case it is time to consider moving to Microsoft SQL Server for the Noah database. Configuring Noah to use SQL Server involves a purchase of SQL Server and expertise in database administration. More details on configuring Noah with SQL Server can be found here.

Reduce the size of the database

Maybe the database has many years of records and significant numbers of patients that are no longer active in the practice. It is possible to reduce the size of the database by deleting patient records.

  1. Use Advanced Search in Noah to set a criteria that will show records not updated or seen in several years. For example, patient with ‘last activity’ prior to 5 years ago.
  • This will produce a search result that can be exported to an nhax for an archive
  • After export, delete the records from Noah. The number of years and the number of patient records will be up to the location.
  • Once records have been removed, run Compact in the Noah Console
  • Finally check the size of the database to determine if enough space has been freed up.

Troubleshoot

Important: If no steps are taken and Noah exceeds the 4 GB size limit, you will find you are no longer able to save data to Noah and may experience errors or corruption of the database.

If this happens follow the steps below to be able to login to Noah and reduce the size of the database.

  1. Verify valid Noah Backups are present. Default Noah backup locations include:
    C:\ProgramData\HIMSA\Noah\Backup\Database
    C:\Program Files (x86)\HIMSA\Noah 4\backup
  2. Get a blank database by following the steps outlined in Solution 6.
  3. Restore a backup
  4. Once you can log into Noah, use the Advanced Search option detailed above to get a group of records that can be removed. Note that the search result can be exported for archive before deleting the patient records.
  5. In this case, when the Noah database is very near corruption, use caution by deleting the patient records one at a time or in very small batches.