IBM Db2 remains one of the most expensive enterprise databases on the market — and one of the most negotiable. PVU-based pricing, complex virtual environment rules, and the credible threat of PostgreSQL migration create multiple levers for reducing Db2 costs significantly. This guide covers Db2 licensing mechanics, edition selection, ILMT compliance, and 8 proven cost optimisation strategies.
IBM Db2 (rebranded from IBM Database 2 and formerly known as DB2) is IBM's primary relational database management system. It is available in multiple editions targeting different use cases and price points, from the free Db2 Community Edition to the enterprise-grade Db2 Advanced Edition.
| Db2 Edition | PVU Limit | Key Features | Approx. List Price/PVU |
|---|---|---|---|
| Db2 Community Edition | 4 cores, 16GB RAM | Full Db2 feature set, no production SLA | Free |
| Db2 Standard Edition | 16 cores | Core RDBMS, HA, standard analytics | £250–£400/PVU |
| Db2 Advanced Edition | Unlimited | BLU Acceleration, in-memory, advanced analytics, pureXML | £600–£900/PVU |
| Db2 Advanced Enterprise Server Edition (AESE) | Unlimited | All Advanced features + DB Admin Tools, Performance Expert | £900–£1,400/PVU |
| Db2 Warehouse | Unlimited (Cloud Pak) | Columnar analytics, MPP, BLU, containerised | Cloud Pak VPC-based |
Many enterprises are running Db2 Advanced Edition or AESE despite only using features available in Standard Edition. An edition right-sizing exercise — auditing which Db2 Advanced features are genuinely in use — is a straightforward cost reduction opportunity. Moving from AESE to Advanced Edition alone can reduce Db2 per-PVU costs by 30–35%.
For IBM's overall licensing framework including PVU mechanics that apply to Db2, see our IBM Software License Negotiation Guide and IBM PVU Licensing Guide.
Db2 is licensed using IBM's PVU (Processor Value Unit) metric. PVUs are assigned per processor core based on the processor technology — Intel x86 cores typically have a PVU factor of 70 per core, while POWER processor cores have PVU factors of 100–120. The total PVU count for a Db2 deployment equals: number of active cores × PVU factor per core type.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
Full-capacity licensing requires you to count all physical cores in the entire server (or logical partition, depending on configuration) — even cores that are not running Db2. For a 40-core server running Db2 on 8 cores, full-capacity requires licensing all 40 cores × 70 PVU = 2,800 PVU.
Sub-capacity licensing allows you to license only the cores actively running Db2, provided you have ILMT (IBM License Metric Tool) deployed and properly configured. For the same scenario, sub-capacity would require only 8 cores × 70 PVU = 560 PVU — an 80% reduction. The difference in licensing cost between full-capacity and ILMT-enabled sub-capacity is often the single largest Db2 cost reduction available.
Without ILMT deployed and properly configured, IBM defaults to full-capacity PVU counting in all audit situations. IBM regularly audits Db2 customers, and ILMT non-compliance consistently results in the largest audit findings. ILMT deployment is not optional for any Db2 organisation that wants to control its licence costs. See IBM ILMT Compliance Guide for full deployment and configuration guidance.
Virtualisation creates the most significant Db2 licensing complexity. IBM's licensing rules distinguish between "hard partitioning" (where virtual machine CPU limits are enforced at the hardware level — allowing sub-capacity counting) and "soft partitioning" (where CPU limits are enforced at the software level — requiring full-capacity counting unless ILMT is used).
VMware is classified as soft partitioning by IBM. Without ILMT, Db2 on VMware requires licensing the entire cluster of physical cores accessible to the VM — not just the cores allocated to the VM. A 3-node VMware cluster with 20 cores per node = 60 physical cores × 70 PVU = 4,200 PVU required for a single Db2 VM, regardless of how many vCPUs are assigned to that VM.
With ILMT deployed, you can sub-capacity license only the vCPUs allocated to the Db2 VM. This makes ILMT deployment on VMware-hosted Db2 an immediate and significant commercial priority. The Broadcom-VMware acquisition and subsequent VMware subscription price increases make some organisations reconsider their VMware strategy entirely — see VMware Alternatives Comparison for context.
KVM (kernel-based virtual machine) is also classified as soft partitioning and has the same ILMT requirement as VMware for sub-capacity Db2 licensing. IBM's approved hard partitioning technologies include IBM PowerVM (for POWER hardware), IBM z/VM (for mainframe), and specific cloud instance types that IBM has certified as hard-partition equivalent. For cloud deployments, always verify the instance type against IBM's current approved cloud capacity list before assuming sub-capacity licensing applies.
ILMT (IBM License Metric Tool) is the required tool for IBM sub-capacity PVU licensing. For Db2 specifically, ILMT must be: deployed on all servers running Db2; configured to scan at least every 30 days; producing signed capacity reports for each measurement period; and accurately reflecting your infrastructure topology.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
Common ILMT configuration errors on Db2 deployments include: incorrect processor type assignment (leading to wrong PVU factor); missed VM scans due to network segmentation; failure to capture Db2 components installed as part of other software; and reporting period gaps that IBM treats as full-capacity periods. For comprehensive ILMT deployment and configuration guidance, see IBM ILMT Compliance Guide.
Db2 is available as a managed cloud service on IBM Cloud (Db2 on Cloud, Db2 Warehouse on Cloud) and increasingly through cloud-hosted options on AWS and Azure via BYOL (Bring Your Own Licence). Comparing cloud database options is an important step before any Db2 renewal negotiation.
| Option | Pricing Model | IBM Support | Annual Cost (medium workload, est.) |
|---|---|---|---|
| Db2 on-premises (licensed) | PVU perpetual + 20% S&S | IBM standard support | £120K–£400K (excl. infrastructure) |
| IBM Db2 on Cloud (managed) | Monthly per instance | IBM managed service | £80K–£200K |
| Db2 BYOL on AWS/Azure | PVU from PA + cloud infrastructure | IBM software, cloud infra | £100K–£250K (infra not included) |
| AWS RDS PostgreSQL | Instance-based, no licence fee | AWS support | £8K–£40K |
| Azure Database for PostgreSQL | Instance-based, no licence fee | Microsoft support | £8K–£40K |
The cost differential between Db2 (perpetual on-premises or managed cloud) and cloud-managed PostgreSQL is typically 5–15x for equivalent workloads. This differential is your primary negotiating anchor when discussing Db2 renewals with IBM.
PostgreSQL is the most mature open source relational database and the primary migration target for Db2 workloads. The technical compatibility between Db2 and PostgreSQL has improved significantly over the past five years, with multiple migration tools, compatibility layers, and managed cloud services reducing migration friction substantially.
PostgreSQL shares much of the ANSI SQL standard with Db2. The primary migration challenges are: procedural SQL (Db2 PL/SQL vs PostgreSQL PL/pgSQL — requires rewrite); specific Db2 functions and operators without PostgreSQL equivalents; Db2-specific data types (particularly pureXML); and application driver changes (JDBC/ODBC configuration). For OLTP workloads with well-structured SQL schemas, migration to PostgreSQL is typically medium complexity — a 2–6 month project for a skilled team.
Several commercial and open source tools accelerate Db2-to-PostgreSQL migration. AWS Schema Conversion Tool (SCT) supports Db2-to-Aurora PostgreSQL migration. EnterpriseDB's Migration Portal handles Db2 schema and query conversion. The open source aws-sct alternative, ora2pg (with Db2 adapters), and pgloader all support various Db2 migration scenarios. Managed migration services from AWS (DMS), Azure (Database Migration Service), and specialist consultancies can execute the data migration phase with minimal downtime.
You don't need to complete a PostgreSQL migration to use it as negotiating leverage. A documented migration assessment with cost estimates, a running PostgreSQL PoC environment, and formal cloud database quotes (AWS RDS PostgreSQL pricing is publicly available) creates a credible alternative that IBM responds to commercially. In most IBM Db2 renewals where PostgreSQL leverage is properly deployed, IBM offers 25–40% additional discount to retain the contract. See IBM to Open Source Migration: Leveraging for Better Pricing for the complete framework.
If you're running Db2 without ILMT on VMware or KVM, you are almost certainly overpaying significantly — and creating audit risk. ILMT deployment and sub-capacity licensing is the highest-ROI Db2 cost reduction action available. For a 200-core VMware environment running Db2 on 20 vCPUs, the difference between full-capacity and sub-capacity is 180 × 70 PVU × Db2 AESE price per PVU — potentially hundreds of thousands of pounds in annual S&S costs alone. Deploy ILMT before your next Db2 true-up or renewal without exception.
Audit exactly which Db2 Advanced Edition features your applications are using. If your workload is standard OLTP with no use of BLU Acceleration, in-memory processing, pureXML, or advanced analytics, you may be able to downgrade from AESE or Advanced Edition to Standard Edition at renewal — reducing per-PVU costs by 30–35%. IBM will resist edition right-sizing at renewal, but it is commercially achievable with negotiation.
Many organisations run multiple Db2 instances across development, test, QA, and production environments, with separate licences for each. Database consolidation — running multiple databases on fewer, larger Db2 instances — reduces total PVU count and associated S&S. For organisations with 10+ Db2 instances, consolidation analysis typically identifies 30–50% PVU reduction opportunities.
Moving critical Db2 workloads to IBM Power hardware with PowerVM enables hard partitioning — eliminating the need for ILMT and enabling finer-grained PVU licensing. For organisations with large VMware Db2 deployments in regulated industries where ILMT is operationally complex, Power hardware with PowerVM can paradoxically be more commercially efficient despite higher hardware costs. Model the full TCO including hardware before comparing.
As described above, a running PostgreSQL proof-of-concept with a subset of your Db2 workload migrated is worth more in negotiations than any price argument. Budget £30K–£80K to implement a meaningful PostgreSQL PoC — the negotiating ROI on this investment is consistently 10:1 or better. Use the PoC results, combined with AWS RDS PostgreSQL pricing, as concrete commercial anchors in Db2 renewal negotiations.
Db2 negotiated in isolation receives far less commercial flexibility than Db2 negotiated as part of a larger IBM Passport Advantage agreement covering multiple IBM products. If you have £500K+ total IBM spend, consolidate your Db2 renewal with your broader PA negotiation to maximise tier leverage and access IBM's senior commercial escalation path. See IBM Passport Advantage Negotiation Strategies for the consolidated approach.
For Db2 workloads with variable or seasonal demand, IBM Db2 on Cloud (managed service) can be more economical than perpetual on-premises licensing when infrastructure costs are properly factored in. IBM Db2 on Cloud pricing is more negotiable than on-premises perpetual pricing for large committed workloads, and the managed service model eliminates administration overhead. Compare Db2 on Cloud pricing against your current on-premises TCO (including infrastructure, DBA staffing, and DR) before assuming on-premises perpetual is cheaper.
IBM Db2 S&S is calculated as 20% of LIASP (Licence Information Adjusted Support Price). For Db2 licences purchased 5+ years ago, the LIASP may have been adjusted upward beyond your original purchase price. Challenge the LIASP for legacy Db2 licences formally — request the LIASP calculation basis and compare against IBM's current Db2 list pricing for equivalent PVU count. LIASP corrections on old Db2 licences regularly produce 10–20% S&S reductions.
Need expert help reducing your IBM Db2 licensing costs?
For the broader IBM cost reduction toolkit, see also: IBM ILMT Compliance Guide, IBM License Audit Guide, and IBM to Open Source Migration Leverage. To understand how Db2 fits within IBM's Cloud Pak strategy and where containerised Db2 Warehouse pricing applies, see IBM Cloud Pak Licensing Guide. For the best IBM negotiation advisors, see Best IBM Negotiation Consulting Firms.
Our matched advisors specialise in Db2 PVU optimisation, ILMT compliance, edition right-sizing, and PostgreSQL migration leverage — consistently achieving 30–50% Db2 cost reductions.