Patrice Perrot
PROGINOV , DBA
La Chevrolière, France
Actions
Patrice Perrot began his OpenEdge career 23 years ago as developer.
he has optimized Progress source since 2005.
he is a DBA at Proginov since 2010.
Dealing with more than 14 000 DB in production, he has to optimize DB, source code and make tool to do .
Links
Area of Expertise
Topics
Our homemade data replication solution in both directions
Using Audit and CDC Feature we are able to replicate our data from several OE 10 Db to OE 11 Db .
This session would be an opportunity for us to present:
Our need for a replication system
How Audit and CDC can be used to replicate data between two databases
How we set things up and put it in production
Tips and tricks, and traps to avoid
CUD Tracking and Transferring
Why "Zero changes to the application" was not fitting our experience
Memory Profiler : How Proginov use this new feature
Progress introduced the backend of the feature Memory Profiler with OE 12.8.
Even if the frontend developed by OpenEdge is not ready now, we developed our own frontend for this feature.
We are using it this feature in production.
In this session, we will explain you how we use Memory Profiler:
- to locate our memory leaks
- to explain the growth of the memory
“Health-monitoring” console
Hosting and managing more than 10k Progress DB in our own Datacenters, we had to design a full-featured process to check their structures, their startup parameters and the performance issues that could happen with accesses made by the 50 000 Progress objects deployed on our application servers.
By taking metrics every five minutes on all of our databases up to every 0.05 seconds for the most active users, our health-monitoring console allows you to:
- Make the link between a huge activity to the source code / block, and even the precise query and if relevant, the concerned index.
- Highlight a user waiting (user wait)
- Prevent a potentially too long transaction (Transaction duration)
- Suggest the improvements of a DB startup parameters ( -n, -L, -B2, ...) before they become critical that will apply online or at the next start
These direct connections between metrics and code/parameters/recommendations lead to very fast and accurate corrective actions.
This session would be an opportunity for us to present:
- The way we take metrics
- How we establish the links between user’s activity and source code
- The management console GUI
- Several other "home-made" tools (Index analysis, locks visualization, …)
- Some Progress functionality use case (Statement caching, diagnostic, …)
- Quick overview of Progress best practices
- How the OE features help us
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top