- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
2 GB file size ceiling
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-06-2008 08:48 PM
Uh oh, what happens when you hit the 2 GB file size ceiling in MAS 90 4.10?
We've got a massive IM5 file and it's making me nervous. It's at around 1.9 GB.
Do we have to purge data? What happens if we don't purge it? Does MAS just lose or overwrite the oldest transactions or does something even creepier happen? Mmmmm, what's creepier than mysteriously losing data....?
Thanks! Schnauzerlove
Re: 2 GB file size ceiling
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-08-2008 04:53 AM
Not sure exactly what happens, but based on conversations with Sage on this topic, you could end up with corrupt or lost data. It does not automatically drop old data.
I would suggest you use the copy company to create an archival company and then purge data from the current company. We had to do this to be able to upgrade. We had to leave an archived company in an old version because it would not upgrade due to file size.
Using MAS200 v4.2 & MAS90 v4.2, FRx (w/Report Server), FRx Webport, & F9
Re: 2 GB file size ceiling
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-08-2008 10:28 AM
When I have had a client hit the 2GB limit in GL (in their detailed transactions file), nothing would post to the GL and they were getting errors. They had to shrink the file first.
Try rebuilding the file (after hours). Sometimes that shrinks the file in size.
Dawn
Re: 2 GB file size ceiling
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
12-19-2008 10:35 AM
I know exactly what will happen from experience; you will get an error 16; probably when updating SO Invoices, PO Reciepts, Work Order Transactions or Bill of Materials Transactions. It can be messy (and probably will be)
PURGE SOON. I would recommend making a backup company first that you can use to lookup transactions prior to your purge date.


