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.
prefetchFactor, Message Buffer Size, MTU…how do all these parameters work together and how should you set them up in your OpenEdge environment?
Part 2 drives home the message with detailed benchmark results across physical and virtual machines and networks.
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.
What is going on with the database!?! Lack of visibility is a complaint we often hear, and ProTop specifically exists to address this complaint. This month we are going to dive into one of the most valuable (and free!) features in ProTop RT: users of a table and users of an index.
In part one, we examined routine tasks scheduled for different times. In this post we’re going to look at special events and the checklists associated with them.
Before we deep dive into OpenEdge client/server performance, let’s make sure everyone is on the same page. This short presentation discusses client/server performance challenges and the tools we’ll use for our benchmarking tests in part 2: Benchmark Results.
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!
