 |
|||||||||
|
|||||||||
|
|
|||||||||
|
We’re not nagging, but Sage products do run far quicker when you
keep them tidy. The software is built around a central database
which, like a giant Leylandii, will simply continue to grow until it
begins to cause problems. So it is prudent to carry out some regular
maintenance work or ‘house-keeping’ before that happens. |
|||||||||
|
|
|||||||||
|
Deleting old spool files Users of Sage Construction and Sage 200 will know that as a report prepares to print, it first creates a spool file which is held in the Sage folder on the server. These files can provide fast access to reports that have been previously created, but allowing them to accumulate indefinitely simply takes up more and more valuable storage space and ultimately impacts the performance of your Sage database.
Our advice:
Speak to Utilize about how and when to delete old spool files Many aspects of your Sage products can be archived or purged on a regular basis to help optimise performance and make life easier for your users. Many of our clients create thousands of new product codes every year without ever deleting the old or unused ones. Imagine how much easier it would be for your users to locate the right product from a neat up-to-date list, not to mention how much better your database might perform.
Our advice:
Speak to Utilize to about archiving old transactions and tidying
product lists.
Sage products create unique reference number lists (or ‘audit trails’) which can prove invaluable from a security perspective to help pinpoint the time and date a given user performed a given task. However, depending on the number of users accessing your Sage products and the volume of transactions being created, these lists can sometimes become very long and impact on your storage and performance in the same way as old redundant spool filers. Our advice: Speak to Utilize about how to keep your URN list tidy. |
|||||||||
|
|
|||||||||
|
|
|||||||||
 |
|||||||||
