Based on Bryan Cheong’s original video. Reviewed 28 September 2026.
Back up SQL Accounting regularly, keep a copy away from the working computer, and check that you can restore it. A backup made two years ago cannot recover transactions entered yesterday.
In this video, Bryan Cheong describes a customer whose computer failed and was reformatted. The most recent available backup was from 2024. Restoring that copy meant reconstructing roughly two years of later transactions. This is the video’s particular case, not a claim that every failed computer has the same recovery outcome.
How to back up SQL Accounting
- Open the correct company account book.
- Select File → Backup Database.
- Check the Backup to location and choose the intended folder.
- Click Backup and confirm completion.
- Check that the resulting file is present and identifiable by company and backup date.
The video shows the core menu path. In current SQL documentation, a storage destination can also be added through the plus button and Add Local Storage. Screens and options can differ between versions.
Keep copies in separate places
Bryan recommends making a local backup, copying it to a removable drive and disconnecting that drive after copying. A drive left connected can be affected by the same malware or equipment problem as the computer.
The video also suggests an additional copy in cloud storage, such as Google Drive or Dropbox. Use storage approved by your business, restrict access to authorised people and check that uploading has completed. A file on the same computer alone provides limited protection if that computer is lost or damaged.
Keep earlier versions and test restoration
Do not rely on a single backup that is repeatedly overwritten. Bryan explains that if yesterday’s file is unusable, an earlier copy may provide another recovery option. A completed backup message is helpful, but a successful restore check is stronger evidence that the copy can be used.
Arrange a restore test in a separate test account book or with technical support. Avoid overwriting the live company database merely to test a file. Check that the restored data includes the expected latest transactions.
How often should you back up?
Bryan recommends daily backups. Make the routine part of the close-of-day process, assign a responsible person and check it consistently. A business entering substantial transactions during the day may need additional recovery points based on how much recent work it can afford to reconstruct.
Frequently asked questions
Is a backup on the same PC enough?
It helps with some mistakes, but it can be lost with the PC. Maintain a separate copy and check recovery.
Should I reformat a failed computer first?
Ask your IT or SQL support provider to assess the situation before making changes that may affect recoverable data. Tell them what backups exist and when they were created.
Official reference: SQL Account Backup & Restore documentation.
Need help with your SQL software?
Syntax Technologies Sdn Bhd provides SQL Accounting and SQL Payroll sales, training and technical support. Contact Syntax with your software version and the task you need help with.


