Welcome to our monthly ProTop newsletter, where you’ll find out what’s new, tips and tricks and other cool ways to use both the free and commercial versions of ProTop.
Today we’re going to take a deep dive into ProTop’s advanced alerting functionality. While the free version of ProTop provides a smorgasbord of data and insight into your OpenEdge environment, the commercial version adds features like alerting that help you sleep better at night.
In Part One, we discussed some of the more well known startup parameters. In today’s blog post, we’ll dig into parameters that are often used incorrectly or simply forgotten.
Every experienced IT person knows that bad things tend to happen on Fridays, and Friday evening is when we got alerted: major performance problems on the primary database server at one of our Enterprise clients.
We often get asked “what’s the magic go fast database parameter setting?” Nobody asks about the go slow settings.
The best way to avoid disasters is to learn from mistakes, preferably someone else’s. Memorize this series or polish your resume-writing skills!
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.
