The Db2 editions and the data product family hide more cost variance than any other corner of the IBM portfolio, and most enterprises cannot tell which edition they actually run.
Db2 in five editions, Informix across the legacy estate, Cognos analytics, InfoSphere DataStage, the newer Db2 on Cloud Pak for Data. We model edition, metric, sub capacity coverage, and the path to a clean position.
Db2 is five different products under one name, and the data portfolio is wider than that.
IBM database licensing covers the Db2 family in its current editions, Informix in the legacy estate, the analytics products in the Cognos family, the data integration estate around InfoSphere DataStage, and the newer container based deployment under Cloud Pak for Data. Each of these has its own metric, its own sub capacity rules, and its own pattern of deployment drift.
Db2 alone ships in Advanced Enterprise Server Edition, Advanced Workgroup Server Edition, Standard Edition, Workgroup Server Edition, and Developer Edition, with significant feature and capacity differences between editions. The pricing is PVU based for the server editions and per authorised user for some workgroup configurations. Customers commonly deploy a higher edition than they purchased because the installer makes it easy and the licence detail is buried in the Passport Advantage agreement.
Our work reconciles entitlement against deployment, validates the sub capacity reporting where ILMT applies, and identifies the path to a clean position. See the related work on sub capacity, ILMT, and Cloud Pak for Data.
The IBM data portfolio we model.
- Db2 AESE, AWSE, Standard, Workgroup, Developer.
- Db2 Connect and Db2 Warehouse.
- Informix Enterprise, Workgroup, Choice.
- Cognos Analytics and Cognos Controller.
- InfoSphere DataStage and Information Server.
- Cloud Pak for Data (VPC).
- Netezza and Performance Server.
The eight week engagement structure.
Edition inventory
Inventory every database product instance against the deployed edition. Reconcile against the Passport Advantage record. Identify edition mismatches and feature usage that crosses an edition boundary.
Metric and capacity reconciliation
For PVU based deployments validate the ILMT bundle and report retention. For authorised user metrics validate the user count. For Cloud Pak for Data validate the IBM License Service coverage. Document the gaps.
Feature usage analysis
Use the database catalog and the IBM diagnostic tools to identify the features in use. Map feature usage to edition. Identify the workloads that justify a higher edition and the workloads that could move down without losing capability.
Position and remediation roadmap
Document the entitled position, the consumed position, and the gap. Build the remediation roadmap that closes the gap at the lowest cost. Identify the renewal moments where the savings can be locked in.
What the diagnostic typically surfaces.
- AESE deployed where Workgroup or Standard would cover the workload.
- Advanced Recovery Feature in use on a non Advanced edition.
- Db2 Warehouse capabilities used on a Db2 server edition.
- Informix instances retired in ops but still on the order.
- Cognos analytics user counts that exceed the entitled user count.
- DataStage jobs running on PVU configurations that should have moved to user metrics.
- Cloud Pak for Data deployment without IBM License Service running.
The structural reasons IBM revisits the data estate.
- Edition mismatches are easy for the auditor to identify.
- Feature usage tracking is in the catalog and visible.
- ILMT bundles for database editions are often partial.
- Container migration changes the metric and the measurement basis.
- Acquisitions bring legacy Informix and Cognos onto the estate.
- User counts drift upward without licence reconciliation.
- Developer Edition gets used in production environments.
How clients approach database licensing.
What is the difference between Db2 AESE and AWSE for licensing?
AESE is PVU based and unrestricted by node count. AWSE is PVU based with a 16 socket limit. Workgroup Server Edition has further restrictions. The pricing varies materially. Edition selection at order time matters.
How do we know which edition we actually run?
The catalog exposes the installed product code and the active features. The diagnostic correlates this against the entitled edition. Edition mismatches are common and well known to IBM.
Does sub capacity apply to Db2?
Yes, for the PVU based editions on supported virtualisation. ILMT is the reporting tool and the same coverage and retention rules apply. See the ILMT page.
What happens when we move Db2 into Cloud Pak for Data?
The metric becomes VPC and the IBM License Service replaces ILMT as the reporting tool. The conversion ratio per source product determines the resulting Cloud Pak entitlement.
Can Developer Edition be used in production?
No. Developer Edition is restricted to development and test use. Production use of Developer Edition is an audit finding and a contract breach.
Resources
Expertise
Services
Need an independent read on this area?
A senior advisor responds within 24 hours and scopes a credible engagement structure within a week.
Get an independent read on this area of your IBM estate.
Tell us where you are in the cycle. A senior advisor will respond within 24 hours with a scoped engagement structure and an availability window. No sales call, no pitch deck. We do not resell IBM software. We have no IBM Business Partner status. Our recommendations are constrained only by what is good for the buyer.
Read more on why independence matters or browse the services overview for engagement structures.
Request a conversation
Corporate email required. Personal email addresses are not accepted.