SAP acquired San Francisco enterprise-information-integration specialist Callixa in approximately August 2005, according to SAP executive Shai Agassi. The transaction became public in an InfoWorld report dated November 30, 2005—about three months after closing. SAP’s stated reason was Callixa’s distributed-query technology, which presented data from databases, files, XML sources and legacy systems through one logical view. The purchase price was not disclosed.
What SAP actually bought
Callixa was a small California software company focused on enterprise information integration. A commercial company profile lists it as founded in 1999 and reports $19.8 million in total funding; those figures come from CB Insights rather than the acquisition report.
The important asset was not a conventional enterprise-resource-planning application or a broad modern integration platform. It was distributed query processing: software that allowed an application to work with multiple heterogeneous sources as though they were one data environment.
How Callixa’s distributed queries worked
The reported model was closer to federated data access than to replication or extract-transform-load processing:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- A developer defined a logical view spanning several sources.
- An application submitted a query against that view.
- Callixa decomposed the request into source-specific operations.
- The operations ran across the underlying systems.
- The engine returned a consolidated result to the application.
The sources described in the 2005 coverage included relational databases, files, XML and legacy systems. Developers could access the capability through SQL, ODBC and JDBC. In practical terms, an SAP application could request a customer or operational view without first copying every record into one physical repository.
This distinction matters. Replication and ETL move or transform data into another location. Distributed querying leaves data in its existing systems and creates a unified logical access layer at query time. The available reporting does not establish whether Callixa supported updates, distributed transactions, caching, materialized views, particular consistency guarantees or modern real-time workloads.
Why SAP wanted ownership
SAP was already licensing distributed-query technology from MetaMatrix. Agassi said SAP wanted to embed the capability more deeply in its own software and eventually phase out the MetaMatrix technology in favor of Callixa’s.
Owning the technology could give SAP greater control over product design, release schedules and integration with its applications. It also reduced dependence on an OEM relationship. MetaMatrix characterized the lost arrangement as a relatively small part of its revenue, but the episode still illustrates a familiar platform strategy: acquire a specialist capability when it becomes important enough to make native.
Where SAP said the technology might go
The 2005 report mentioned several possible destinations:
- Business-intelligence software
- Portal software
- Business applications
These were prospective uses, not a documented product roadmap. The available account does not identify every shipping product, release date, customer deployment or later fate of Callixa’s technology. It therefore would be inaccurate to claim that the acquisition directly became SAP’s current Integration Suite.
Was Callixa an SAP master-data-management acquisition?
Contemporary commentary disagreed. Aaron Zornes of the CDI Institute interpreted the purchase as potentially useful to SAP’s master-data-management efforts. Agassi explicitly rejected that interpretation and said the acquisition was not related to SAP’s MDM products.
The most accurate conclusion is that MDM was an analyst interpretation, not SAP’s stated purpose. Callixa’s ability to expose a unified view of fragmented information could be relevant to data-management projects, but that does not prove the deal was an MDM acquisition.
The timing and human story behind the deal
SAP had not publicly discussed the purchase before the InfoWorld report. Agassi’s statement that it had closed about three months earlier places the transaction around August 2005; November 30 was the report date, not necessarily an announcement date.
Rank #4
Callixa’s earlier history was unusually difficult. The company had been preparing a product launch at the World Trade Center on September 11, 2001, and the report said at least three senior employees were killed in the attacks. Callixa temporarily closed, later reopened and eventually sought a buyer. Dina Bitton, identified as its former chief technology officer, joined SAP Labs as a vice president—evidence that the transaction involved technical leadership as well as software.
What is confirmed—and what is not
| Question | What the record supports |
|---|---|
| Who was acquired? | Callixa Inc., a San Francisco enterprise-information-integration vendor. |
| When did it close? | Approximately August 2005, inferred from Agassi’s “about three months” statement before the November 30 report. |
| Why did SAP buy it? | To obtain distributed-query technology and bring that capability into SAP’s own products. |
| How much did SAP pay? | Not disclosed in the available coverage. |
| What happened to MetaMatrix? | SAP said it would eventually phase out the licensed MetaMatrix technology; completion and timing are not established here. |
| Did Callixa become SAP Integration Suite? | Not established. SAP’s current platform has a much broader scope and no direct product lineage is documented in this record. |
Why the acquisition still matters
Callixa addressed a problem that remains recognizable: important information was scattered across incompatible systems. Its 2005 answer was federated access—querying those systems through a common logical layer instead of demanding one consolidated database.
The terminology and product categories have since expanded. SAP now describes SAP Integration Suite as a cloud platform covering application and process integration, APIs, events, B2B scenarios, hybrid environments and related governance. That is broader than the distributed-query capability described in the Callixa coverage and should not be treated as proof of a direct continuation.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsBest Value
For anyone evaluating a similar requirement today, the first question is architectural: is the need federated query access, data virtualization, ETL or ELT, workflow orchestration, API management, or B2B connectivity? Modern platforms such as SAP Integration Suite, Boomi and Workato overlap in integration capabilities, but none should be assumed to reproduce Callixa’s historical query model one-for-one.
Primary source
The acquisition details, technology description, MetaMatrix relationship, personnel information and MDM disagreement come from InfoWorld’s November 30, 2005 report, “SAP picks up integration vendor Callixa.”
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
