At this point our application SX.e is customized to the point of being hard to recognize. Our team of developers if both experienced and capable (4 people with almost 10 years each in Progress -- in a company of 140 people), that is not a concern. They understand the logic and how it flows, and what can and cannot be archived.
So while we use a standard ERP package, if any person familiar with the product came to our company, it would be hard to recognize. We have a significant amount of information that is rarely needed, and segregating this to another area seems like the best means to reduce backups and assist in speeding up and reducing report size.
I am in no way concerned about their ability in my department.
Why do this outside my already stated reason. We work in distribution of software, which readily discontinues products, however history of these transactions can't be purged (some non-licensing software can). So all of these products while no longer current need require an extensive number of notes and other information will rarely be required, but must be retained.
We aren't doing a simple dump of data because within the programs (and RTB) we can find the programs that manage the information we need, and also any associated information to coincide with that. So while we could dump pos for seven years back, however, since product info doesn't have a date to key off of, we would have to dump all the products as well (and effectively creating two records in different locations). We have a discontinue date to work with, but as I mentioned above, discontinued doesn't mean we can delete it.
Some of this could be stated incorrectly, however, my intent when posting was not to put myself in a position defending the developers actions. Believe me they are more than capable.
-- and I agree with this being a departure from the original topic, I appreciate your comments.
The Progress version, we are working towards, we are in the midst of installing Optio, and it is not a small project.