Running IBM software? Third-party support cuts IBM costs by 50–90%. Free cost analysis, no obligation.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
IBM Informix: The Installed Base IBM Does Not Talk About
IBM Informix remains one of the world's most widely deployed relational database engines despite decades of IBM's strategic focus shifting elsewhere. The installed base is concentrated in sectors where Informix was the de facto standard before Oracle and SQL Server consolidation: core banking transaction processing, clinical information systems (CIS), insurance policy administration, and telecommunications real-time rating and billing.
The reason Informix persists is straightforward: the applications built on it are deeply integrated, the data models are complex, and the migration cost to PostgreSQL, Db2, or any other platform is a multi-year, multi-million-pound project that frequently delivers minimal business value. The database is working. IBM is the problem.
IBM's support strategy for Informix has followed the familiar playbook: price increases, support degradation, extended support fees for older versions, and persistent sales pressure toward IBM Cloud and Db2. For organisations that cannot or will not migrate, third-party support removes IBM from the equation entirely.
Informix Version Matrix and EOS Status
| Informix Version | Release Year | IBM EOS Date | TPS Availability |
|---|---|---|---|
| Informix 11.10 | 2007 | Ended Sep 2014 | ✓ Full TPS |
| Informix 11.50 | 2009 | Ended Sep 2014 | ✓ Full TPS |
| Informix 11.70 | 2011 | Ended Sep 2018 | ✓ Full TPS |
| Informix 12.10 | 2014 | Ended Sep 2023 | ✓ Full TPS |
| Informix 14.10 | 2018 | EOS Sep 2028 | ✓ TPS available now (pre-EOS saving) |
Informix 12.10: The Largest EOS Cohort
Informix 12.10 reached end-of-support in September 2023 and represents the single largest cohort of Informix installations still in production. IBM's Extended Support pricing for 12.10 — available for an additional fee — is typically 50–100% above standard S&S rates. Most organisations paying IBM Extended Support fees for 12.10 could switch to TPS today and save more than the Extended Support surcharge in year one.
TPS Coverage for IBM Informix
The most common concern about Informix TPS is whether an independent provider can support Informix's proprietary features — particularly its ANSI SQL compliance layer, time series data capabilities, spatial extensions (Geodetic DataBlade), and the SPL (Stored Procedure Language) that many legacy applications depend on. In practice, TPS covers the full production scope of Informix environments:
- Database engine — all Informix engine versions, Dynamic Server (IDS), and Informix SE, including OLTP optimisation and OLAP workloads
- High-Availability Data Replication (HDR) — primary/secondary HDR configuration, log shipping issues, failover troubleshooting, and RSS (Remote Standalone Secondary) replication
- Stored procedures and SPL — all SPL stored procedures, triggers, UDRs (User Defined Routines), and C-language UDFs registered in the database
- DataBlade modules — Geodetic DataBlade, TimeSeries DataBlade, ESRI Spatial DataBlade, and other registered DataBlade modules
- INFORMIX-4GL applications — legacy 4GL application support where the runtime depends on the Informix engine layer
- Security patches — CVE patches backported to your current version without requiring upgrade
- Performance and stability — buffer pool tuning, onstat diagnostics, checkpoint configuration, and schema optimisation
4GL Application Support: A TPS Differentiator
Many organisations running Informix 11.x or 12.x have INFORMIX-4GL applications that are functionally critical and have not been rewritten in decades. The combination of Informix database + 4GL runtime creates a support dependency that commercial support vendors rarely accommodate. GoVendorFree TPS covers the Informix engine layer that 4GL applications depend on, and our engineers have direct experience with 4GL runtime behaviour under Informix 11.x and 12.x.
TPS Cost Model — Four Deployment Profiles
| Profile | Environment | IBM S&S/yr (est.) | TPS/yr (est.) | Annual Saving |
|---|---|---|---|---|
| Regional financial services | Informix 12.10, 2-server HDR, core banking | £120,000 | £48,000 | £72,000 (60%) |
| NHS Trust / mid-size healthcare | Informix 11.70 + 12.10, CIS + PAS | £210,000 | £78,750 | £131,250 (63%) |
| Telco billing platform | Informix 12.10 HA cluster, real-time rating | £480,000 | £172,800 | £307,200 (64%) |
| Large enterprise multi-instance | Informix 12.10 + 14.10, multiple business units | £960,000 | £336,000 | £624,000 (65%) |
For organisations on IBM Extended Support (post-EOS Informix 12.10), the base comparison should be Extended Support rates — which are typically 20–50% above standard S&S. TPS savings relative to Extended Support fees are proportionally larger.
Paying IBM Extended Support for Informix 12.10?
The Extended Support surcharge alone often exceeds what you would pay for full TPS coverage. Get a precise comparison within 48 hours.
Get Your Informix Assessment IBM Licensing GuideMigration: The Cost That Stops Most Projects
IBM's preferred narrative is that Informix customers should migrate to Db2, PostgreSQL-compatible IBM databases, or cloud-native alternatives. What IBM does not quantify is the cost of doing so. For a mid-size financial services organisation running a core banking application on Informix 12.10, a migration to Db2 or PostgreSQL involves:
- Schema migration — Informix's data types (including SERIAL, DATETIME, INTERVAL, and BYTE/TEXT large object types) require mapping to the target database engine, with custom migration scripts for non-standard types
- SPL to PL/SQL or PL/pgSQL — stored procedure logic in SPL must be rewritten; automated conversion tools exist but produce code that requires manual review, testing, and optimisation for every procedure
- DataBlade replacement — organisations using TimeSeries or Geodetic DataBlades face the most complex migration path; IBM has no direct Db2 equivalent for the TimeSeries DataBlade, and the Geodetic DataBlade requires PostGIS or similar extension evaluation for any PostgreSQL migration
- Application-layer testing — JDBC/ODBC connection string changes, query behaviour differences (particularly around Informix's FIRST N / SKIP N syntax and implicit lock mode behaviour), and exception handling differences all require application regression testing
Realistic migration timelines for a mid-size Informix deployment (50–200 databases, 2–5 critical applications) range from 18 months to 4 years, with project costs of £800,000 to £4M+. Against this backdrop, TPS is not a delay — it is the rational commercial decision during strategic planning.
Industry Angles
Financial Services: Informix dominates the core banking installed base of several European regional banks and building societies, typically running transaction processing, GL posting, and nostro/vostro reconciliation. The combination of Informix's row-level locking model and HDR replication has proven highly reliable for OLTP workloads. Migration risk for these organisations is existential — TPS buys the time needed for a properly planned, phased transition.
Healthcare (NHS and private): Multiple NHS Trusts run Informix-backed Patient Administration Systems (PAS) and clinical information systems, particularly legacy systems from iSOFT, Meditech, and RiO. NHS Digital's DSPT obligation requires demonstrable security patch management — TPS provides CVE patches on the Informix version in production without requiring a version upgrade that could break clinical system certification.
Telecommunications: Informix's TimeSeries DataBlade was widely deployed for CDR (Call Detail Record) storage and real-time rating in telco billing platforms. Organisations that built their billing engine on Informix TS face a particularly complex migration because the TimeSeries data model has no direct equivalent in most alternative databases. TPS maintains the operational platform while the commercial billing system replacement programme is evaluated.
Transition Process
Transitioning an IBM Informix environment to TPS typically completes in 3–5 weeks. IBM requires no minimum notice period for Informix S&S termination (unlike Oracle's 30-day requirement), which simplifies the transition timeline.
- Environment documentation: Version inventory, HDR/RSS topology, DataBlade catalogue, and stored procedure count
- IBM relationship assessment: Any open PMRs (Problem Management Records) should be resolved or documented before SnS termination; any active IBM software audits should be disclosed at this stage
- TPS contract execution: Coverage scope confirmed, SLA agreed, contact protocols documented
- Knowledge transfer: Configuration documentation, known issues, and any special environment characteristics transferred to TPS team
- Go-live: 15-minute response SLA active from IBM S&S termination date