Sage 300 needs to be cleaned & tidied up from time-to-time.

Sometimes Sage 300 needs to be cleaned up, as opposed to the oft-seen strategy of “ignore it until the problem goes away” which – surprise – doesn’t work. Cleaning up Sage 300 starts with centralizing data files and reports.

Here are some of our established best practices and protocols.

1. Determine database performance. Sage 300 uses an MSSQL database in most circumstances, and its performance has the most overall impact on how clean Sage 300 is running.
2. Clear the history in Sage 300 for data that is not needed.
   • Identify the module and data that needs a cleanup
   • Backup the existing database before performing this step. (Set it up as a new company or database for archive lookups)
   • Perform the clear history function for each module – this is a Sage built-in feature
   • Run data integrity checks on Sage 300
3. Run the daily, monthly and yearly Sage 300 tests & cleanups.

• Daily
• Weekly
• Monthly