Sage 50 Rebuilds
What happens when your Sage dataset gets very big, say with 200k transactions or more. If you haven’t or cannot upgrade to the latest version of Sage 50 – version 21 or 2015, then you may have to rebuild the data. We have done a number of these rebuilds this year already – mainly for clients with Handheld devices or other 3rd party software which pours sales transactions back into Sage 50.
The rebuild procedure involves the clearing out of all transaction history in Sage (after creating an archive for lookup) and importing the outstanding customer and supplier invoices at the financial year-end. After the rebuild the client has a clean dataset with a small number of transactions with much faster searching and reporting. With a rebuild, the client also has the facility to redo the Chart of Accounts, remove unwanted customers, suppliers and stock records.
We probably will have less of this work to do in the future as clients upgrade to version 2015 with its capacity to store a dataset with over 1 million transactions.