Are Your Data Files Reaching Their Limit?
Published
FundWare’s backend data is made up of both Cobol data files and a SQL database. The Accounts Receivable 7 and Budget Prep data resides completely within the SQL database, whereas other modules, such as General Ledger, Accounts Payable, and Payroll, have pieces both in the SQL database and Cobol data files. The Cobol data lives in the data files within the FundWare\Data folder and start with the division number.
The size limitation of the SQL database is limited only by the version of SQL installed and the amount of free space on the hard drive. The Cobol files, however, have their own individual size limitations. Each Cobol file stores specific pieces of data and some of these files are prone to reach their size limitation after several years of data entry if data is never purged from the system.
These files have been seen to reach their limit when they are around one gig in size. For a file like the CSK, with a record length of 160, this equates to about 6,500,000 records as the maximum. With a record like the CSK, which holds General Ledger transaction data, this limit can be reached after years of posting journal entries.
How do I know if any of my files are reaching their limit?
The best way to check is to look at the file sizes in the FundWare\Data folder. Check for any files getting close to that one gig mark. The CSK, CSL, and PYL files are the most common files to reach their limit first, as they hold the most transactional data for General Ledger and Payroll.
If any of your files do reach their limit you will receive an error in the system when trying to post additional data into that file. The error will generally show the file name along with the error code or stat number 24 or 9024. Most commonly this is seen when trying to post a journal entry to a CSK file that has reached its limit: 02CSK 24.
What do I do if one of my files has reached its limit and how do I prevent a file from getting to that point?
If a file is reaching, or has reached, its limit, then transactions will need to be purged from the system to make free space for new data. Below are Knowledgebase solutions on how to purge different types of data from FundWare:
Before purging any data, you can archive your division. This will copy the division to another division number that can be kept for historical purposes. If you copy your division to another division number before purging, the pre-purged data will remain untouched in the new division, which can be logged into if any historical information is needed. For more information on copying divisions see How to create a test division.
If you have a lot of historical data in your FundWare system, being mindful of file size limits and knowing whether or not data needs to be purged can save a lot of frustration from an entry not posting because there is no room for it in the data file!
The size limitation of the SQL database is limited only by the version of SQL installed and the amount of free space on the hard drive. The Cobol files, however, have their own individual size limitations. Each Cobol file stores specific pieces of data and some of these files are prone to reach their size limitation after several years of data entry if data is never purged from the system.
These files have been seen to reach their limit when they are around one gig in size. For a file like the CSK, with a record length of 160, this equates to about 6,500,000 records as the maximum. With a record like the CSK, which holds General Ledger transaction data, this limit can be reached after years of posting journal entries.
How do I know if any of my files are reaching their limit?
The best way to check is to look at the file sizes in the FundWare\Data folder. Check for any files getting close to that one gig mark. The CSK, CSL, and PYL files are the most common files to reach their limit first, as they hold the most transactional data for General Ledger and Payroll.
If any of your files do reach their limit you will receive an error in the system when trying to post additional data into that file. The error will generally show the file name along with the error code or stat number 24 or 9024. Most commonly this is seen when trying to post a journal entry to a CSK file that has reached its limit: 02CSK 24.
What do I do if one of my files has reached its limit and how do I prevent a file from getting to that point?
If a file is reaching, or has reached, its limit, then transactions will need to be purged from the system to make free space for new data. Below are Knowledgebase solutions on how to purge different types of data from FundWare:
- How to purge/save a Fiscal Year
- How to purge Payroll History and Terminated employees
- How to purge inactive vendors
- How to purge paid invoices
Before purging any data, you can archive your division. This will copy the division to another division number that can be kept for historical purposes. If you copy your division to another division number before purging, the pre-purged data will remain untouched in the new division, which can be logged into if any historical information is needed. For more information on copying divisions see How to create a test division.
If you have a lot of historical data in your FundWare system, being mindful of file size limits and knowing whether or not data needs to be purged can save a lot of frustration from an entry not posting because there is no room for it in the data file!
News
ARCHIVED | Financial Edge® Tips and Tricks
04/26/2013 11:40am EDT
Leave a Comment