Search results

The first problem that you will have is that it is not available for version 9.

All of the Progress documentation is online: https://docs.progress.com/category/openedge-archives

OpenEdge 10 certainly has lots of support for XML. OE10 is 20 years old now and hasn't been a "current" release for a long, long time. I'm too lazy to look it up but I don't think that OE10 has much if any explicit JSON support. OTOH, JSON output is pretty trivial to create. Parsing JSON input...

What version of Progress are you using? If your Progress release is older than XML (or JSON) then, no, it won’t be supported. If your Progress release is reasonably modern then, yes, it is supported.

Aside from the Windows performance considerations... a more fundamental reason to not overwrite the old backup is that, as soon as you start the new backup the old one that you are overwriting is unusable. And if something goes wrong before the new backup completes you are without a valid...

IOW - target 12.8 for any migration.

It sounds like you have a fairly complex setup. You might want to engage an experienced consultant rather than try to work it out in an online forum ;) Incidentally, and apropos of nothing - I'm going to be in Europe for the next couple of weeks.

That's too bad. Is the vendor at least still providing support and bug fixes and willing to move you to a modern OE release? To use the horizontal table partitioning approach someone will need to write some code and either compile it onsite or provide r-code. If you have an onsite compiler...

Do have access to the source code?

Just be aware that that technique requires the horizontal table partitioning add-on and that could create problems with older code if the old code uses RECID in inappropriate ways (almost all usage of RECID is inappropriate).

The space in a block freed by deleting records will be reused as new records are added (and if old records grow). For index blocks you need to run idxcompact to reclaim the space. (That can be done online.) There are many ways to dump and load. Some methods can greatly reduce the required...

The original post says: True, the concern is the speed of those tasks and there are ways to improve that stuff which do not involve purging data but I actually found this rationale to be a refreshingly solid set of reasons for wanting to purge. The more typical reasons usually boil down to...

IMHO if it takes more than an hour you need better disks.

... and if you do have such a policy to follow - make sure to destroy the old backups.

Data _can_ be a liability. Keeping it beyond legally mandated record retention periods can expose you to needing to provide it during legal "discovery" processes. Which can be fairly onerous in terms of work to be done to extract it, review it, and prepare it for whoever wants it. Whereas if...

You might want to share who the manufacturer is. Someone may be familiar with them and have specific advice. In any case, OEM provided storage area configurations are frequently "substantially less than optimal". Is "10.7" the application version number? (That's not a valid OpenEdge version...)...

As Patrice says - this won't work as you wish. When you delete data you also probably won't create much in the way of "free" and "empty" blocks so you are not going to see much evidence in prostrct db statistics either. To reclaim disk space you will need to dump & reload. And if you are...

"Oh Eee Oh Ex Oh Dee" has a nice rythm to it. I like it!

Oh Eee Oh Ex Oh Dee

I nominate Cecil as the new head of OE Marketing!