Of course this probably won't be free, so your company has to decide which are the most important issues overall, both to rescue archived data and storing future data. Keep enough backup copies so they can also reconstruct as much as possible.
It's not going to go away and data will continue to be corrupted until it's fixed.Īlso, it sounds like some of your archive has already been corrupted and lost. But now that they know, they ought to get down to business and determine how best to fix the issue and quick. Apparently they hadn't been bitten by this issue before.
For them not to be aware of the 2GB limit does not necessarily mean they're not good programmers. They should have anticipated this eventuality. Oops, I better not say any more, I don't want to do your vendor's work for them. If it needs to stay in one big bucket so-to-speak, then you can still keep one huge master lookup table but add a field (or use a unique existing one) as a key so the program cn determine which of a group of tables with the memo fields is desired. If the division will be visible to the user, figure out how best to split it apart, possibly by year, type of event, or some other intuitive manner. (2)If it all must stay accessible, especially since you described it as already being an archive, the data will have to be split into 2 or more tables.
(1) Remove and archive some of the data that is not longer needed. So likely there are two major ways to handle this.