This case study describes how a pharmaceutical company saved six million dollars over the term of its Oracle agreement by optimising its database estate before the renewal rather than negotiating the renewal in isolation. Details have been anonymised and figures rounded, but the method is repeatable. The lesson is that the biggest database savings often come not from the negotiation itself but from fixing the technical estate that drives the licence requirement before sitting down with Oracle.
This article sits within our case studies pillar and illustrates the principles behind our contract review service.
The Starting Position
The company ran a sprawling Oracle Database estate built up over years of acquisitions and projects, with Enterprise Edition deployed widely and numerous option packs enabled across dozens of servers. Its costs were high and rising, and the database administrators were focused on keeping systems running rather than tracking the licensing implications of how those systems were configured. The renewal was approaching, and the assumption was that the cost was simply the price of running Oracle at scale.
The first insight was that the licence requirement was a function of the technical estate, and the technical estate had grown without licensing discipline. Servers were over provisioned, options were enabled that were not used, and workloads were spread across more cores than they needed. Each of these inflated the licence count, and each could be addressed before the renewal, the same approach we describe in our Enterprise Edition discount tactics article.
Auditing the Option Usage
The team conducted a detailed audit of which database options and management packs were actually enabled and which were genuinely used. The findings were striking: several chargeable options, including tuning and diagnostic packs, had been enabled on servers where no one used them, often switched on by default or during troubleshooting and never turned off. Each enabled option was a licensable exposure and a cost driver, regardless of whether it delivered any value.
The audit found chargeable options enabled on servers where they were never used. Disabling the unused options before the renewal removed both a compliance exposure and a significant slice of the licence requirement, and it had to be done carefully to avoid disrupting production.
Disabling the unused options, carefully and with proper change control, removed both the compliance risk and the cost they implied. This required close coordination between the database team and the licensing analysis, because the people who could turn off the options did not know they were chargeable, and the people who understood the licensing did not control the servers. Bridging that gap is central to the discipline we set out in our Oracle Database product guidance.
Consolidating the Server Estate
Alongside the option audit, the team consolidated workloads onto fewer, appropriately sized servers. The estate had grown organically, with databases spread across more physical cores than the workloads required, and because Oracle Database is licensed by processor, every unnecessary core was an unnecessary cost. By consolidating and right sizing, the company reduced the core count that drove its licence requirement without affecting performance.
The consolidation was planned to respect the partitioning and counting rules that determine how Oracle measures the licence requirement, so the reduction was real and defensible rather than a configuration that an audit could challenge. Getting these rules right is essential, because a consolidation that ignores them can create exposure rather than reduce it, a risk we examine in our processor licence counting article.
The Outcome
By the time the company entered the renewal, its genuine licence requirement was substantially lower than its historical position, because it had removed the unused options and consolidated the estate. The renewal was then negotiated against this leaner, accurate footprint rather than the inflated one, and the combination of a reduced requirement and a well prepared negotiation produced savings of around six million dollars over the agreement term.
The savings came from two sources working together: the technical optimisation that reduced what the company needed to licence, and the negotiation that secured good terms on that reduced footprint. Either alone would have helped, but together they compounded, which is why we treat estate optimisation and negotiation as a single connected exercise rather than separate ones, as set out in our database renewal tactics article and our database licensing guidance.
What Other Buyers Can Take From This
The transferable lesson is to fix the estate before negotiating the renewal. Many customers negotiate hard on a licence requirement that is itself inflated by unused options and over provisioned servers, winning a discount on a number that should never have been so high. Auditing option usage and right sizing the estate first reduces the requirement at its source, and a discount on a smaller, accurate footprint is worth far more than a bigger discount on a bloated one.
The case also underlines the value of bridging the technical and commercial sides. The savings depended on the database team and the licensing analysis working together, because neither could deliver the result alone. Coordinating that work, and ensuring the optimisation respects Oracle's counting rules so it survives scrutiny, is exactly what we do on these engagements, guided by the framework in our Oracle Negotiation Playbook.
Where to Read Next
For a database migration outcome see our retail chain migration case study. The full set of outcomes is in our case studies pillar, and the methodology behind them is in the Oracle Negotiation Playbook.