Quantcast
Channel: Sage 50 US
Viewing all articles
Browse latest Browse all 18012

Blog Post: Is it Year End time? Let’s talk about purging your database.

$
0
0
From the time you started using Sage 50 - U.S. Edition you have been busy inputting new records into the database; from customer invoices and receipts, vendor bills and checks, to time tickets and payroll checks. You may have noticed a decline in the speed and performance of your database as the years have gone by. As you are preparing to close the fiscal and/or calendar year, its a good idea to check the database size and do some “clean-up”, this is when the Purge process comes in handy. Purge is the process of removing inactive maintenance records and transactions from a company, reducing the size of the company and improving performance. A purge is recommended once your company's size exceeds 300MB. As your company gets larger over time, purging may become a necessity in order to maintain optimal program performance. You can check your database size by clicking the  'Help' menu, selecting 'Customer Support and Service', then 'File Statistics'. This window will show you the size for each file in your database and at the bottom you will see the Grand Total. The Purge process can be performed at any time, including after closing the fiscal or calendar year. Depending on data size, the purge process can take quite a while, so it is recommended to perform it at the end of the day and let it run overnight. For best performance, it is recommended to start Purge process on the computer that stores the company data, if you're in a network environment. It is also recommended that you perform a series of purges, rather than doing it all at once; for example, if your data goes back to the year 2000, try purging through 12/31/2000, then the next day purge through 12/31/2001, and so on. For step by step instructions, click here Thanks

Viewing all articles
Browse latest Browse all 18012

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>