Posts by:
Paul Koufalis is the President of White Star Software. He began his OpenEdge DBA career more than 25 years ago after completing a Computer Engineering Degree at McGill University. Today, he’s known for his pragmatic and ROI-centric approach when working with White Star’s global client base. When he’s not staring at his multiple immense computer screens (how much is too much?), you can probably find him speaking at a Progress event somewhere in the world or being roughed-up by his twin boys back home in Montreal.
People often ask us: “what tasks should an OpenEdge DBA be performing? When? What should my daily, weekly, quarterly, etc. checklist have on it?”
In this video Tom describes how you can monitor very active sessions in your OpenEdge environment.
There are many. Let’s start with a few CPU-related metrics, then we’ll tackle memory, disk, kernel, network and more in later blog posts.
The DBA equivalent of buying flowers for your wife – more is better…to a point. You want it to be big enough to hold the “working set” of data: the orders, invoices, pick-lists, etc. that your business needs right now to function efficiently.
Poor transaction scope and BI growth: the evil twins conspiring to crash your database! Take our word for it…we know.
Sometimes it’s bad code, sometimes it’s bad luck, but either way, Tom shows you how to protect your business against the potentially disastrous effects of out-of-control transactions.
Are you using fixed length extents in your OpenEdge database? What happens if they fill? Will anybody notice?
The -hash parameter is one of those little-known, often misunderstood parameters that can cause you a LOT of pain if set incorrectly. Trust us, we’ve seen it kill performance on numerous occasions!
Check out the video below and JC’s blog post “The Smoking Gun” (2021-07-05) where he talks about a real-world production environment where they just couldn’t figure out why performance was sooooo bad!
