The Commercialization of Database Management Systems, 1969–1983

The Commercialization of Database Management Systems, 1969–1983 Thomas J. Bergin American University Thomas Haigh University of Wisconsin, Milwaukee Database management systems were the most important commercial software packages of the 1970s. The authors reconstruct their early history by examining the evolution of their capabilities and installed base. They also document early user experiences, including the sources from which potential users learned about these new technologies, new roles such as the database administrator, and new concepts such as the data dictionary. One approach to examining the early days of characteristics and exploring the changing commercial database management systems dynamics of the DBMS marketplace into the (DBMSs) is to study the evolution of the lead- early 1980s. This includes a brief discussion ing DBMS packages of the 1970s. Doing so, of the commercial threat posed by relational we can reconstruct the technical issues and database systems to established products and management decisions facing information efforts made to add relational capabilities to technology managers as they investigated traditional products such as IDMS. Our focus the new world of database software in the is on database management packages for early 1970s. This includes not only the IBM machines, which dominated the main- DBMS as a productivity aid for application frame market at that time. We rely here on programmers but also the new jobs, such as contemporary market-analysis reports, partic- database administrator, created by the tech- ularly Datapro’s ‘‘Buyer’s Guide to Data Base nology and the managerial challenges of cre- Management Systems’’ starting in 1974.1 ating a shared and consistent database to be used across different departments. Indeed, Database beginnings during the 1970s, the DBMS existed both as Life in the data processing departments of a tangible technology (with considerable the 1960s revolved around applications strengths and pronounced weaknesses) and requiring the storage, updating, and retrieval as the symbol of a movement to raise the sta- of large volumes of data. The arrival of disk tus of computing within the managerial technology in the mid-1960s posed a huge world and establish the idea of data as a cor- challenge to application developers.3 Organi- porate resource. (See the ‘‘Data Management zations struggled to exploit the potential of Definitions’’ sidebar for a brief explanation random access data storage and interactive of related terminology.1) query. As historian Martin Campbell-Kelly noted, Corporate data processing budgets mush- finding good data on software adoptions and roomed in the 1960s, driven in large part by usage is difficult.2 Our research utilizes vari- the rapidly growing cost of maintaining sys- ous contemporary journal and newsletter tems and application software. Organizations articles, consulting reports, and advisory not wanting to continue to create and main- guides to document early DBMS user experi- tain large applications had two choices: hire a ences and the processes by which they eval- contractor to develop the software to the uated different packages. We also examine organization’s specifications or purchase a some of the major DBMS products of standard software package from an indepen- the 1970s, documenting their technical dent vendor (and in many cases, pay them 26 IEEE Annals of the History of Computing Published by the IEEE Computer Society 1058-6180/09/$26.00 c 2009 IEEE Data Management Definitions To frame our discussion on specific software pack- and centralize the data storage, the system’s principal ages, let’s review a pair of definitions from the period: intent is to perform such functions as information retrieval, report generation, and inquiry for single DBMSs can be defined as those that are intended to applications.1 manage and maintain data in a non-redundant structure for the purpose of being processed by multiple Data-management systems were also known as file- applications. A DBMS organizes data elements in management systems. Although we provide a short dis- some predefined structure and retains relationships cussion of file-management and report-generation soft- between different data elements within the database. ware, largely to clarify the continued success these A data management system, on the other hand, is in- products enjoyed throughout the 1970s, this article fo- tended primarily to permit access to and retrieval cuses on early mainframe database management soft- from pre-existing files (usually for a single applica- ware. We believe the history of data management tion). Although a data management system might systems is sufficiently important to warrant a separate provide the capability to minimize data redundancy investigation. to tailor the package to the buyer’s environ- its applications, and save money. Infosystems, ment). In the mid-1960s, however, the soft- one of the leading management-oriented ware services industry was in its infancy, data-processing publications, assured its read- and almost no commercial market existed ers in 1973 that database systems were like for standard software packages such as sort the aeronautical efforts of the Wright broth- utilities, report writers, and information- ers; although carefully planned early efforts retrieval packages. When vendors and user had ‘‘never developed much lift when ap- groups did create such software, it was plied to the practical realities of processing given away without additional charge. large files that had to be stored, indexed Two factors changed this state of affairs. and sorted with live data,’’ they were now On 7 April 1964, IBM announced the System/ poised to rise majestically into the air.9 The 360, a family of compatible computers and problem was that no one knew much about operating systems (OSs) that let users mi- them, even the organization that had grate to larger computers without throwing attempted to write generalized data access out their existing programs.4 With these, software.10 organizations relied heavily on standard Most organizations wanting to explore OSs provided by computer vendors. Then DBMSs needed training for their technical on 6 December 1968, IBM announced that staff and consultants to guide them. Initially, it was unbundling software products, systems there was not much help available, so con- engineering services, and training costs rather sulting firms and software vendors realized than supplying them free of charge to its cus- that educating potential clients was an im- tomers with the hardware lease or purchase.5 portant way to spread their message, sell Together these decisions provided the products, and build market share. Technical foundation for the software products and ser- training, off-the-shelf software, and various vices industry’s growth. The creation of com- types of support services became part of the patible computer systems families gave growing software industry. prospective software developers a large and Industry periodicals of the early 1970s growing market in which to sell their wares. contained numerous articles introducing the IBM’s unbundling meant that early software notion of DBMSs. Datamation and Computer- vendors would not have to compete with world printed tutorials, articles detailing free software from IBM.6 This environment early user experiences, and articles focusing not only motivated software entrepreneurs on specific software packages.11 Some brave to create software, it allowed the fledgling authors (and editors) published short case industry to flourish. By 1972, there were studies as well as articles comparing individ- 82 vendors offering 275 packages for the life ual software packages and introduced readers insurance industry.7 Indeed, Cincom (Total), to advanced concepts.12 We say ‘‘brave’’ be- Informatics (Mark IV), and CIM (Datacom/ cause vendors were constantly changing DB) began as software services firms.8 their offerings while working with existing DBMS software promised to reduce the customers to plan future improvements and organization’s hardware burden, speed up additions. EDP Analyzer brought a new October–December 2009 27 History of DBMS management and organizational viewpoint than rely on (out-of-date) monthly or quar- to the dialogue.13 Most users, however, terly hardcopy reports? Identifying these depended on their hardware vendors. Of always-changing requirements was not a triv- course, industry periodicals, consultants, ial process and required the attention of and reports were not the only ways for poten- senior personnel. tial users to learn about advances in database After defining the organization’s require- technologies and share practical experiences ments, the selection team had to compare with its implementation. Computer user the hardware and software needed to run groups, particularly SHARE and GUIDE, con- the various DBMS packages with their cur- tinued to play an important role, with rent hardware configuration and operating many sessions organized to discuss current system and estimate the cost of additional and forthcoming software. hardware, software, media, training, and per- As databases emerged as a distinct research sonnel. Although all vendors were happy to area, new specialized interest groups, jour- demonstrate their products, some vendors nals, and professional meetings were created. encouraged users to benchmark their prod- For example, the ACM created a Special Inter- ucts against their competitors, and this est Group on File

Load more