Historical notes on relational database management system pioneer Ingres (once called Relational Technology, Inc.). Related subjects include:
In my recent Stonebraker-oriented post about database theory and practice over the decades, I wrote
I used to overrate the importance of abstract datatypes, in large part due to Mike’s influence. I got over it. He should too. They’re useful, to the point of being a checklist item, but not a game-changer. A big part of the problem is [that] different parts of a versatile DBMS would prefer to do different things with memory.
and then left an IOU for a survey of abstract datatypes/RDBMS extensibility. Let’s get to it.
Perhaps the most popular term was actually object/relational DBMS, but I’ve never understood the etymolygy on that one.
Although I call RDBMS extensibility a “checklist item”, the list of products that can check it off is actually pretty short.
- PostgreSQL has the granddaddy implementation.
- Its ideas were commercialized as Illustra, which was bought by Informix, which later was bought by IBM.
- Oracle has one of the major implementations.
- IBM has one of the major implementations.
- Sybase has struggled with implementing the technology.
- So did Microsoft SQL Server, which of course started with the Sybase code line.
Surely there are more, but at the moment I can’t really think of which they are.
|Categories: Database management systems, IBM, Informix, Ingres, Microsoft, Oracle, Sybase||2 Comments|
As part of my series on the keys to and likelihood of success, I’d like to consider some historical examples in various categories of data management.
A number of independent mainframe-based pre-relational DBMS vendors “crossed the chasm”, but none achieved anything resembling market dominance; that was reserved for IBM. Success when they competed against each other seemed to depend mainly on product merits and the skills of individual sales people or regional sales managers.
IBM killed that business by introducing DB2, a good product with very good strategic marketing from a still-dominant vendor. By “very good strategic marketing” I mean that IBM both truly invented and successfully market-defined the relational DBMS concept, including such conceptual compromises as:
- Ted Codd’s 12 rules, not that anybody — even IBM — actually followed them all.
- SQL as the standard, rather than the probably superior QUEL.
In the minicomputer world, however, hardware vendors lacked such power, and independent DBMS vendors thrived. Indeed, Oracle and Ingres rode to success on the back of Digital Equipment Corporation (DEC) and other minicomputer vendors, including the payments they got to port their products to various platforms.* The big competitive battle was Oracle vs. Ingres, about which I can say for starters: Read more
Recently I expressed doubts about Actian’s DBMS-conglomerate growth strategy. For context, perhaps I should review other DBMS vendors’ acquisition strategies in the past. Some — quite a few — worked out well; others — including many too minor to list — did not.
In the pre-relational days, it was common practice to buy products that hadn’t succeeded yet, and grow with them. Often these were programs written at enterprises, rather than third-party packages. Most of Cullinet’s product line, including its flagship DBMS IDMS, was came into the company that way. ADR, if memory serves, acquired the tiny vendor who created DATACOM/DB.
Then things slowed down. A Canadian insurance company oddly bought Computer Corporation of America, to utter non-success. (At least I got an investment banking finder’s fee on the deal.) Computer Associates, which did brilliantly in acquiring computer operations software, had a much rockier time with DBMS. It acquired Cullinet, Applied Data Research, and ASK/Ingres — among others — and didn’t have much growth or other joy with any of them.
Indeed, Ingres has been acquired three times, and hasn’t accomplished much for any of the acquirers (ASK, Computer Associates, Actian).
I used to think that Oracle’s acquisition of RDB provided key pieces of what became Oracle’s own extensibility technology. Andy Mendelsohn, however, disputed this vehemently — at least by his standards of vehemence — and his sources are better than mine. Rather, I now believe as I wrote in 2011:
… while Oracle’s track record with standalone DBMS acquisitions is admirable (DEC RDB, MySQL, etc.), Oracle’s track record of integrating DBMS acquisitions into the Oracle product itself is not so good. (Express? Essbase? The text product line? None of that has gone particularly well.)
Experiences were similar for some other relational DBMS pioneers. Read more
|Categories: Applied Data Research, ASK Computer Systems, Computer Associates, Cullinet, Database management systems, IBM, Informix, Ingres, Microsoft, Oracle, Sybase, Teradata||2 Comments|
I blogged a little last year about the rewards and challenges of combining professional services and software in a mature company’s business model. My main example was Oracle. But other examples from Oracle’s history might have been equally instructive. For example:
- Oracle started out doing what amounted to custom development for government (military/intelligence) clients.
- Even when Oracle said it had productized its software, the stuff didn’t work very well without services to get it running.
- Oracle and Ingres both got a huge fraction of their early revenue* from deals to port their software to various brands of hardware. That’s a lot like professional services.
- Oracle’s huge Tools Group grew out of professional services, if I have the story straight. Indeed, its first product was written by later long-time group chief Sohaib Abbasi when he was a consultant.
Roland Bouman reminded us on Twitter of an old post I did on another blog about Ingres history, the guts of which was:
Ingres and Oracle were developed around the same time, in rapidly-growing startup companies. Ingres generally was the better-featured product, moving a little earlier than Oracle into application development tools, distributed databases, etc., whereas Oracle seems to be ahead on the most important attributes, such as SQL compatibility — Oracle always used IBM’s suggested standard of SQL, while Ingres at first used the arguably superior Quel from the INGRES research project. Oracle eventually pulled ahead on superior/more aggressive sales and marketing.
Then in the 1990s, Ingres just missed the DBMS architecture boat. Oracle, Informix, Microsoft, and IBM all came out with completely new products, based respectively on Oracle + Rdb, Informix + a joint Ingres/Sequent research project, Sybase, and mainframe DB2. Ingres’s analogous effort basically floundered, in no small part because they made the pound-wise, penny-foolish decision to walk away from a joint venture research product they’d undertaken with innovative minicomputer vendor Sequent in the Portland, OR area.
Computer Associates bought Ingres in mid-1994, and immediately brought me in to do a detailed strategic evaluation. (Charles Wang telephoned the day the acquisition closed, in one of the more surprising phone calls I’ve ever gotten, but I digress … Anyhow, the relevant NDA agreements, legal and moral alike, have long since expired.) There was nothing terribly wrong with the product, but unfortunately there was nothing terribly right either. Aggressive investment — e.g., to get fully competitive in parallelism and object/relational functionality, the two biggest competitive differentiators in those days — would have been no guarantee of renewed market success.
Notwithstanding the economic question marks, CA surprised me with its enthusiasm for taking on these technical challenges. But another problem reared its head — almost all the core developers left the company. (If you weren’t willing to sign a noncompete agreement that was utterly ridiculous in those days, at least in the hot Northern California market, you couldn’t keep your job post-merger.) And so, like almost all CA acquisitions outside of the system management/security/data center areas, Ingres fell further and further behind the competition.
Some of the same information made it into my post here on Ingres history later the same year, but for some reason not all did.
The top PostgreSQL-related April Fool’s joke this year, which seems to have successfully pranked at least a few people, was that Postgres is dropping SQL in favor of an alternative language QUEL.
Folks, QUEL was the original language for Postgres. And Ingres. And, more or less, Teradata.* I’d guess Britton-Lee too, but I don’t recall for sure.
*Once upon a distant time, when I was a cocky young stock analyst, I explained to Phil Neches, chief scientist of Teradata, just why it was a really good business idea to drop T-QUEL for SQL. I doubt he was convinced quite on that day, more’s the pity.
The idea of specialized hardware for running database management systems has been around for a long time. For example, in the late 1970s, UK national champion computer hardware maker ICL offered a “Content-Addressable Data Store” (or something like that), based on Cullinane’s CODASYL database management system IDMS. EDIT: See corrections in the comment thread. (My PaineWebber colleague Steve Smith had actually sold – or at least attempted to sell – that product, and provided useful support when Cullinane complained to my management about my DBMS market conclusions.) But for all practical purposes, the first two significant “database machine” vendors were Britton-Lee and Teradata. And since Britton-Lee eventually sold out to Teradata (after a brief name change to ShareBase), Teradata is entitled to whatever historical glory accrues from having innovated the database management appliance category.
My deal when I blogged at Computerworld was that I could reuse my stuff if I linked to them. Below is the meat of a post about Michael Stonebraker I made in May, 2005.
Edit: There’s now a whole Michael Stonebraker section on DBMS2.
I’m probably going to mention Mike Stonebraker’s name in one or more other blog entries soon, and not necessarily in the context of always agreeing with him. So I’d like to take a moment to point out that he’s the greatest living contributor to database technology, and this may even have been true when Dr. E. F. “Ted” Codd was still alive.
Along with Eugene Wong and grad student Jerry Held, Mike founded and ran the INGRES research project at UC Berkely, which directly spun off the company later known as Ingres, Oracle’s chief direct competitor in its early years. One of his key lieutenants (and successors) was Bob Epstein, who designed Sybase‘s database technology, which is also the core of Microsoft‘s DBMS. Jerry Held went on to run much of development at Tandem, starting with Non-Stop SQL, the first industrial-strength relational DBMS, and later ran the database products for Oracle.
Mike himself went on with the POSTGRES project, which introduced an approach to user defined functions and abstract data types that swept the DBMS industry. POSTGRES begat Illustra, which was acquired by and became integral to the products of Informix, where Mike also served as CTO. Informix’s database technology was of course later taken over by IBM.
That’s quite a track record, although there are also a couple of more or less failed startups along the way. …
The IEEE awarded Mike its most recent John von Neumann medal, which seems to be a big deal. Here’s the citation.
- Official-looking Ingres Project history
IBM. With BOMP and D-BOMP, IBM was probably the first company to commercialize precursors to DBMS. (BOMP stood for Bill Of Materials Planning, foreshadowing the hierarchical architecture of IMS.) Out of those grew DL/1 and IMS, IBM’s flagship hierarchical DBMS, and the world’s first dominant DBMS product(s). Of course, IBM also innovated relational DBMS, via the research of E. F. “Ted” Codd, then some prototype products, and eventual the mainframe version of DB2. To this day DB2 on the mainframe remains one of the world’s major DBMS, as does the separate but related product of DB2 for “open systems.”
Cincom. In the 1970s, Cincom was probably the most successful independent software product company. Its flagship product was Total, a shallow-network DBMS that was a little more general than the strictly hierarchical IMS. What’s more, Total ran on almost any brand of computer hardware. Cincom remains independent and privately held to this day.
Cullinane/Cullinet. Charlie Bachman innovated a true network DBMS at Honeywell, but it didn’t turn into a serious product at that time. B. F. Goodrich, however, ran a version. This is what John Cullinane’s company bought and turned into IDMS, which at least on the mainframe supplanted Total as the technical, mind share, and probably revenue market leader. Cullinet (as it was then called) ran into technical difficulties, however, losing ground to the more flexible index-based DBMS. It was eventually sold to Computer Associates.
A lot of software industry leaders cut their teeth at Cullinet, notably Andrew “Flip” Filipowski, later the colorful founder of Platinum. Other alumni include Renato “Ron” Zambonini, Dave Litwack, Dave Ireland, and the original PowerBuilder development team. John Landry and Bob Weiler ran the firm for a while toward the end, but they don’t really count; rather, they’re the most prominent alumni of applications pioneer McCormack & Dodge.
Note: Index-based is a term I used in and probably coined for my first report in 1982, comprising both inverted-list and relational RDBMS, as opposed to the link(ed)-list hierarchical and network products such as IMS, Total, and IDBMS. The companies that beat Cullinet were long-time rival Software AG, and then especially Applied Data Research; then all three of those independents were blown out by IBM’s DB2. And then the whole mainframe DBMS business was in turn obsoleted by the rise of UNIX … but I’m getting ahead of my story.
Software AG. Like Cincom, Germany-based Software AG is a 1970s DBMS pioneer that has always remained independent and privately held. Sort of. Twice, Software AG of North America was spun off as a separate, eventually public company. Software AG’s flagship DBMS was the inverted list product ADABAS. SAP’s MaxDB was also owned by Software AG for a while (and seemingly by every other significant German computer company as well – or more precisely, by Nixdorf where it was developed, and by Siemens after it bought Nixdorf).
I actually visited Software AG in Darmstadt once. Founder Peter Schnell and key techie Peter Page were both gracious hosts. Schnell was proud of their new building, and especially of the hexagon-based wooden dual desks he’d personally designed. General analytic rule – when the CEO is focused on the décor, this is not a good sign for the company’s near-term prospects. (I call this having an “edifice complex.”)
Applied Data Research (ADR). ADR is often credited as being the first independent software company, having introduced products in the late 1960s and prevailed in antitrust struggles against IBM to allow the business to survive. Basically, it sold programmer productivity tools. This led it to acquire Datacom/DB, an inverted-list DBMS developed in the Dallas area. In the early 1980s, Datacom/DB began to boom, and was on a track to surpass both IDMS and ADABAS in market share until DB2 showed up and blew them all away. ADR was particularly aided by its fourth-generation language (4GL) IDEAL, which was an excellent product notwithstanding the famous State of New Jersey fiasco. (As John Landry said to me about that one, “4GLs are powerful tools. In particular, they allow you to write bad programs really quickly.”)
ADR was an underappreciated powerhouse, boasting all of the Fortune 100 as customers way back in the early 1980s (yes, even archrival IBM). When the DBMS business stalled, however, ADR was quickly sold — first to Ameritech (the Illinois-based Baby Bell company), and soon thereafter to Computer Associates.
Computer Corporation of America (CCA). CCA’s DBMS Model 204 may have been the best of the prerelational products, boasting an inverted-list architecture akin to that of ADABAS and Datacom/DB. The company was also interesting in that it was first and foremost a government contract research shop, and hence did all sorts of interesting prototype work that sadly never got commercialized. In about 1983 it became that the company wasn’t going anywhere, and it put itself up for sale.
I was personally instrumental in that decision. Our investment banker pretended he was considering taking CCA public. CCA President Jim Rothnie showed us revenue projections. I asked how he had gotten them. He replied that he had taken the market size projection 5 years out, assumed 10%, and drawn a “plausible curve.” However, I quickly got Socratic with him. “How many salesmen do you have?” “How much revenue does the average experienced salesman produce?” “How many experienced salesmen do you expect to have next year?” “How high do you think their average productivity can grow?” “Let us multiply.” (Yes, I really said that. I can be a jerk. And anyway Jim was the sort of analytic guy one can say that to without giving serious offense.)
CCA was sold to a Canadian insurance company whose name I’ve now forgotten. Eventually, it was spun back out (perhaps after some intermediate changes of ownership), and resurfaced as primarily a data integration company, called Praxis.
In the real old days (mid 1970s, perhaps), Model 204 was resold by Informatics (later Informatics General, later the hostile takeover that became the guts of Sterling Software, which like so many other companies was eventually absorbed into Computer Associates). I know this because Richard Currier used to sell the product when he worked at Informatics. That probably makes Richard and me about the only two people who still remember the fact.
Hmm. I forgot to mention Intel’s System 2000. Well, truth be told it was a dying product even back when I first became an analyst in 1981, and I recall nothing about it, except Gene Lowenthal’s observation that Intel had had trouble selling chips and DBMS through the same salesforce. I think Al Sisto, who I probably met when he was head of sales at RTI (Relational Technology, Inc. — later called Ingres), came out of that business, but I’m not 100% sure. I remember Pete Tierney from that RTI management team more clearly anyway, although that’s mainly because we stayed in touch at subsequent companies over the years.
|Categories: Applied Data Research, Computer Associates, Cullinet, Database management systems, IBM, Ingres, McCormack & Dodge, Oracle, Software AG, System software||1 Comment|
The news about Ingres being spun off by Computer Associates brings back a lot of memories. First of all, Ingres (then called Relational Technology Inc.) was one of the centerpieces of my first-ever research trip to the West Coast in April, 1982. Second, the day CA’s acquisition of Ingres closed, Charles Wang (CA’s CEO, of course), called me personally and asked me to consult to CA about their forthcoming product strategy. It was an intense, month-long project, perhaps still the single largest one I’ve ever done.
So with no further ado, here some observations of and about Ingres through the years.
- Ingres was of course the first of several DBMS companies spun off from UC Berkeley’s INGRES research project, and one of several started with Mike Stonebraker’s involvement. I wrote about that history briefly in my now-defunct Computerworld blog.
- Ingres (then called RTI) and Oracle (then called RSI, for Relational Software Inc.) were of course arch-rivals. As a general rule, Ingres was first to market with new features such as a 4GL or a truly distributed DBMS. Oracle, however, was the first to market with the features customers most cared about, at a level of completeness they found acceptable. Eventually, when Sybase was a factor too, Ingres was always betwixt and between — everybody’s second choice, but not the first choice of enough buyers to keep on prospering. (Later on in the 1990s, Gupta took over the Ingres role in the low-end market — the product was broader than Powersoft, but who cared?)
- Ingres was eventually merged into ASK Computer Systems. While surely a distraction, that’s not what killed it. Each predecessor company had its own problems, and they pretty much stayed out of each other’s way, at least in product strategy. What killed them is that neither side of the business managed to stay fully competitive in product.
- Ingres’s fatal technological mistake was whiffing on parallelism. And it did so in the most painful of ways. Ingres had a joint development project going in the Portland, OR area with Sequent, to develop a parallelized version of their DBMS. They pulled out due to expense, and Informix stepped in. And that’s how Informix managed to be competitive with Oracle in parallel processing, while lack of competitiveness in that area is what doomed Sybase and Ingres. Ouch!!!
- A second Ingres failing probably wasn’t as big as I thought at the time. This was an inability to offer abstract datatypes, aka object/relational, aka UDBMS (where the “U” is for “universal”). I thought this feature would be hugely important, and my opinion on that score probably was a big part of influencing Informix to overpay for Illustra. But Microsoft has never had the feature, and it doesn’t seem to have suffered all that much in the marketplace for its lack.
- ASK was doing even worse on the product side than Ingres — it never came out with a decent GUI version of the product, although ASK did get a license to resell Baan’s code — and the whole sorry mess was eventually sold to CA. CA has a well-deserved reputation for slashing development costs and profiting from slowly-dying software products. But I watched this acqusition from the inside, and to this day I think they really wanted to make the product competitive. But there was one not-so-little problem …
- … CA ran off all of Ingres’s engineers right after the acquisition. CA’s policy upon acquiring companies was requiring employees who wanted to keep their jobs to sign non-compete agreements. In Ingres’s case, however, that policy was a spectacular failure. Oracle, Informix, Sybase, and much of IBM’s DBMS development were all located in the Bay Area. Finding another local job for these guys (and gals) was EASY. Competitors went into a feeding frenzy hiring Ingres engineers, and there was essentially NOBODY left. In my judgment there was a reasonable chance CA could revitalize development with an aggressive investment strategy, but they ultimately blinked. And with very limited ongoing development, the product obviously faded quickly as a mainstream competitor.
I think I’ll go write about the rest of the story over in the DBMS 2 blog.