Context
A Sage installation reaching its limits
The Sage 100 Accounting installation—deployed four years before our involvement—only allowed five fiscal years to be open simultaneously. The MS SQL Server Express database had reached its size limit, leading to application issues.
Several updates had not been applied, and there were no backup mechanisms in place, manual or automated.
Solutions
Taking over and applying best practices
The client was stuck: they had hit Sage’s limit of five active fiscal years, and couldn’t archive the oldest one because the SQL Server Express database had reached its 10 GB limit.
We upgraded SQL Server from the Express edition to the Standard edition. This allowed the archiving of the oldest fiscal year, along with permission corrections on the database.
After that, the client was able to begin their new fiscal year. On our end, we implemented a daily automated backup of the database.
Results
Business continuity restored, deployment under control
The Sage 100 Accounting deployment is now fully documented and kept up to date. We’ve taken over responsibility for Sage updates, resolved the issue related to the five-year limit by enabling archiving. Also, we ensured continuity of operations through reliable backups.
Back to case studies
