Skip to content

Service

Performance tuning

We find the 5% of SQL that burns 80% of your database.

The problem

The system "got slow" and every team blames another one: the vendor says it is the database, the DBA says it is the application, infrastructure says it is the network. Meanwhile users wait 40 seconds for a screen and management wants to buy a bigger server. In most cases hardware is not the problem.

How we work

  1. 1

    Evidence-based diagnosis

    AWR and ASH reports for the problem window, wait profile, top SQL by CPU, I/O and executions. We identify the real cause before proposing changes.

  2. 2

    Quick wins

    Missing indexes, stale statistics, unstable execution plans, mis-sized parameters. Low-risk changes with immediate impact.

  3. 3

    Deep optimization

    Rewriting critical SQL and PL/SQL, partitioning, SQL Plan Baselines, memory tuning (SGA/PGA) and the application tier when the cause is there.

  4. 4

    Measurement

    We compare AWR before and after. You get real response times, not impressions.

Frequently asked questions

Do we need the Diagnostics Pack?

AWR and ASH require a Diagnostics Pack license (Enterprise Edition). If you do not have it, we work with Statspack, V$ views and 10046 traces, which deliver equivalent results with more manual work.

Can you tune without changing application code?

Largely yes: indexes, statistics, baselines, parameters and configuration solve a large share of problems. When the cause is application SQL, we hand you the proposed rewrite for the vendor to incorporate.

How long does a diagnosis take?

The initial diagnosis takes 3 to 5 business days with access to the database and its reports. Quick wins are usually applied in the first week.

Do you work with non-Oracle databases?

Oracle is our specialty. We can do a high-level assessment of SQL Server or PostgreSQL, but it is not our focus.