Blue Frontier StudioContact usA week of sampling, then a second week to measure the changes
Pinpoint your Oracle database's bottlenecks.
We sample a week of load and your heaviest SQL, then send a document of suggested changes.
After your team has tested and applied them, a second week of sampling shows what each change did.
Four steps
Step 1, one week
Sample the load
A read-only collector samples the load for a week, including your heaviest SQL and its execution plans.
Step 2
Find the causes
We rank what costs the most time and work out a suggested change for each.
Step 3
Get the suggestions
Indexes, statistics, SQL rewrites and settings, in a document you can copy from, each with its reason.
Step 4, after your team applies them
Measure the change
A second week of sampling, compared with the first, shows what each change did.
What you get
- Your heaviest SQL, ranked by the time it uses, with its execution plans
- Suggested changes: indexes, statistics, SQL rewrites and database settings
- The statements for each change, ready to test, with the reason for it
- A before-and-after comparison, from the same readings taken twice
What stays with your team
- Testing every change on a non-production copy first
- Applying the changes in production
- Changes to application code that a rewrite needs
- Hardware and storage decisions: we report what the sampling shows
Test before productionTest every suggestion on a non-production copy first.
We make no changes on production.
We make no changes on production.
No Diagnostics or Tuning Pack neededThe collector reads only V$ views that every Oracle licence includes.
It does not use AWR, ASH or the SQL Tuning Advisor.
It does not use AWR, ASH or the SQL Tuning Advisor.
Launch discount: 25% offIn return for an anonymous case study.
Before you ask
Do we need the Diagnostics or Tuning Pack?No.
The readings come from views every Oracle licence includes, such as V$SQLSTATS.
The readings come from views every Oracle licence includes, such as V$SQLSTATS.
Will the sampling slow the database down?It is a few light queries on a schedule, run as a read-only user.
Who applies the changes?Your team, after testing them, in your own change window.
What if the gain is small?The before-and-after numbers show it, change by change, and you decide which to keep.
Talk to us about your database
Send a short message through the contact form.
We reply within one business day to set up a call.