Ingres Project

Ingres Project
Name	Ingres Project
Developer	University of California, Berkeley; Ingres Corporation; Computer Associates; Actian Corporation
Released	1970s
Latest release version	varies
Programming language	C (programming language); Assembly language
Operating system	Unix; VMS; Microsoft Windows
Genre	Relational database management system
License	Proprietary software; Open-source software

Ingres Project The Ingres Project began as an academic research effort that produced a family of relational database management systems influential in the development of SQL-based systems, PostgreSQL, and commercial offerings from multiple companies. Originating at a major American research university, the project influenced database theory, query optimization, and transaction processing used by enterprises, government agencies, and software vendors. Over decades the project intersected with several corporations, standards bodies, and derivative open-source initiatives, shaping the landscape of data management.

History

The project started in the early 1970s at University of California, Berkeley under the guidance of researchers associated with the System R and relational model movements, including faculty and graduate students influenced by the work of Edgar F. Codd. Early milestones included prototypes developed on DEC PDP-11 and Berkeley Software Distribution platforms, and academic papers presented at conferences such as ACM SIGMOD and VLDB. In the late 1970s and 1980s, technology transfer led to the foundation of commercial entities like Ingres Corporation and later acquisitions involving Computer Associates, affecting product direction and licensing. Splinter projects and forks spawned systems such as Postgres—which later evolved into PostgreSQL—while other branches were adopted by organizations including NASA, Raytheon, and financial firms. Throughout the 1990s and 2000s, standards work with ISO/IEC and industry groups such as ANSI and participation in initiatives like ODBC and JDBC reflected ongoing influence. Recent decades saw shifts between proprietary offerings and open-source releases overseen by vendors like Actian Corporation.

Architecture and Design

The system's architecture emphasized a relational engine implementing concepts from relational algebra and the Codd model, with a query processor, storage manager, and transaction subsystem. The storage layer supported page-oriented file systems on hosts including UNIX System V and Microsoft Windows NT, interfacing with buffer managers and recovery managers inspired by designs from System R and Ingres Research Group publications. Query optimization used cost-based planners influenced by work from researchers affiliated with IBM Research and University of California, Berkeley, incorporating access path selection, join ordering, and use of indices such as B-tree variants standardized by Donald Knuth-era algorithms. Concurrency control implemented locking protocols comparable to two-phase locking and integrated logging and recovery techniques similar to ARIES, enabling ACID properties on hardware produced by vendors like Intel Corporation and Sun Microsystems.

Features and Functionality

Feature sets across project derivatives included support for a SQL dialect alongside host-language interfaces such as Embedded SQL and APIs conforming to ODBC and JDBC. The systems provided index types, integrity constraints, and transaction isolation levels relevant to enterprise deployments like those at AT&T and General Electric. Extensibility features led to procedural languages and user-defined functions akin to later additions in Oracle Database and IBM Db2. Tools for import/export, backup, and replication paralleled utilities in Informix and Sybase ASE, while performance monitoring options echoed capabilities found in Microsoft SQL Server and SAP environments. Security controls adapted to standards followed by agencies such as National Institute of Standards and Technology.

Development and Community

Development originated in academic groups at University of California, Berkeley and expanded into corporate engineering teams at Ingres Corporation, Computer Associates, and Actian Corporation. The community included academics, commercial engineers, and open-source contributors who published at venues like ACM SIGMOD, ICDE, and VLDB. Derivative projects such as Postgres attracted contributors later affiliated with University of California, Berkeley, University of California, Santa Cruz, and companies including Amazon Web Services and Red Hat. Standards engagement brought interactions with ISO/IEC JTC 1 committees and industry consortia. Conferences, mailing lists, and code repositories facilitated collaboration among database researchers and practitioners from organizations including Bell Labs and Microsoft Research.

Commercialization and Products

Commercial incarnations were marketed by entities such as Ingres Corporation and, following acquisitions, Computer Associates and Actian Corporation. Products targeted enterprise customers in sectors like banking and telecommunications, competing with Oracle Corporation, IBM, Microsoft, Sybase, and Informix. Licensing models ranged from proprietary enterprise editions to open-source community editions and OEM integrations used by firms such as Siemens and Honeywell. Professional services and certification programs paralleled offerings from Accenture and Deloitte for migration, tuning, and support. Over time, product lines evolved to include cloud-ready deployments and connectors for middleware from Tibco and Apache Software Foundation projects.

Use Cases and Adoption

Adoption encompassed transaction processing, reporting, and decision-support workloads in organizations like NASA, Department of Defense (United States), and multinational banks. Use cases included online transaction processing for airline reservation-style systems, data warehousing tasks similar to Business Intelligence deployments at retailers, and embedded database roles inside telecommunications equipment from vendors like Ericsson. Academic use persisted in database research and teaching at institutions including Stanford University and Massachusetts Institute of Technology. Migration paths from the project’s systems informed movement to modern platforms such as PostgreSQL and cloud services from Amazon Web Services and Google Cloud Platform.

Category:Relational database management systems