Efficient Query Processing for Data Integration

Total Page:16

File Type:pdf, Size:1020Kb

Efficient Query Processing for Data Integration Efficient Query Processing for Data Integration Zachary G. Ives A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy University of Washington 2002 Program Authorized to Offer Degree: Department of Computer Science and Engineering University of Washington Graduate School This is to certify that I have examined this copy of a doctoral dissertation by Zachary G. Ives and have found that it is complete and satisfactory in all respects, and that any and all revisions required by the final examining committee have been made. Chair of Supervisory Committee: Alon Halevy Reading Committee: Alon Halevy (chair) Daniel Weld Dan Suciu Date: In presenting this dissertation in partial fulfillment of the requirements for the Doc- toral degree at the University of Washington, I agree that the Library shall make its copies freely available for inspection. I further agree that extensive copying of this dissertation is allowable only for scholarly purposes, consistent with “fair use” as prescribed in the U.S. Copyright Law. Requests for copying or reproduction of this dissertation may be referred to Bell and Howell Information and Learning, 300 North Zeeb Road, Ann Arbor, MI 48106-1346, or to the author. Signature Date University of Washington Abstract Efficient Query Processing for Data Integration by Zachary G. Ives Chair of Supervisory Committee: Professor Alon Halevy Computer Science and Engineering A major problem today is that important data is scattered throughout dozens of sepa- rately evolved data sources, in a form that makes the “big picture” difficult to obtain. Data integration presents a unified virtual view of all data within a domain, allowing the user to pose queries across the complete integrated schema. This dissertation addresses the performance needs of real-world business and sci- entific applications. Standard database techniques for answering queries are inappro- priate for data integration, where data sources are autonomous, they generally lack mechanisms for sharing of statistical information about their content, and the envi- ronment is shared with other users and subject to unpredictable change. My thesis proposes the use of pipelined and adaptive techniques for processing data integration queries, and I present a unified architecture for adaptive query processing, including novel algorithms and an experimental evaluation. An operator called x-scan extracts the relevant content from an XML source as streams across the network, which enables more work to be done in parallel. Next, the query is answered using algorithms (such as an extended version of the pipelined hash join) whose work is adaptively scheduled, varying to accommodate the relative data arrival rates of the sources. Finally, the sys- tem can adapt the ordering of the various operations (the query plan), either at points where the data is being saved to disk or in mid-execution, using a novel technique called convergent query processing. I show that these techniques provide significant benefits in processing data integration queries. TABLE OF CONTENTS List of Figures iii List of Tables v Chapter 1: Introduction 1 1.1 The Motivations for Data Integration . 2 1.2 Query Processing for Data Integration . 5 1.3 Outline of Dissertation . 10 Chapter 2: Background: Data Integration and XML 12 2.1 Data Integration System Architecture . 12 2.2 The XML Format and Data Model . 16 2.3 Querying XML Data . 20 Chapter 3: Query Processing for Data Integration 25 3.1 Position in the Space of Adaptive Query Processing . 26 3.2 Adaptive Query Processing for Data Integration . 28 3.3 The Tukwila Data Integration System: An Adaptive Query Processor . 33 Chapter 4: An Architecture for Pipelining XML Streams 36 4.1 Previous Approaches to XML Processing . 40 4.2 The Tukwila XML Architecture . 42 4.3 Streaming XML Input Operators . 50 4.4 Tukwila XML Query Operators . 58 4.5 Supporting Graph-Structured Data in Tukwila . 61 4.6 Experimental Results . 66 4.7 Conclusions . 81 i Chapter 5: Execution Support for Adaptivity 83 5.1 An Adaptive Execution Architecture . 87 5.2 Adaptive Query Operators . 94 5.3 Experiments . 101 5.4 Conclusions . 107 Chapter 6: Adaptive Optimization of Queries 109 6.1 Convergent Query Processing . 113 6.2 Operators for Phased Execution . 119 6.3 Implementation within Tukwila . 122 6.4 Experiments . 127 6.5 Conclusion . 135 Chapter 7: Tukwila Applications and Extensions 137 7.1 Data Management for Ubiquitous Computing . 137 7.2 Peer Data Management . 139 7.3 Integration for Medicine: GeneSeek . 142 7.4 Summary . 143 Chapter 8: Related Work 145 8.1 Data Integration (Chapter 2) . 145 8.2 XML Processing (Chapter 4) . 148 8.3 Adaptive Query Processing (Chapters 5, 6) . 152 Chapter 9: Conclusions and Future Directions 158 9.1 Future Work in Adaptive Query Processing . 159 9.2 Envisioning a Universal Data Management Interface . 161 Bibliography 166 ii LIST OF FIGURES 1.1 Data warehousing and integration compared . 4 2.1 Data integration architecture diagram . 13 2.2 Sample XML document . 17 2.3 XML-QL graph representation of example data . 18 2.4 XQuery representation of example data . 19 2.5 Example XQuery over sample data . 21 2.6 Results of example query . 22 3.1 Architecture diagram of Tukwila . 33 4.1 Tukwila XML query processing architecture . 44 4.2 Example XQuery to demonstrate query plan . 46 4.3 Example Tukwila query plan . 47 4.4 Encoding of a tree within a tuple . 48 4.5 Basic operation of x-scan operator . 52 4.6 The web-join operator generalizes the dependent join . 57 4.7 X-scan components for processing graph-structured data . 63 4.8 Experimental evaluation of different XML processors . 69 4.9 Wide-area performance of query processors . 71 4.10 Comparison of data set sizes and running times . 73 4.11 Scale-up of x-scan for simple and complex paths . 74 4.12 Experimental comparison of XML vs. JDBC as a transport . 77 4.13 Comparison of nest and join operations . 78 4.14 Scale-up results for x-scan over graph and tree-based data . 80 4.15 Query processing times with bounded memory . 80 5.1 Example of query re-optimization . 86 5.2 Example of collector policy rules . 95 iii 5.3 Performance benefits of pipelined hash join . 103 5.4 Comparison of Symmetric Flush vs. Left Flush overflow resolution . 105 5.5 Interleaved planning and execution produces overall benefits . 106 6.1 Example of phased query execution for 3-way join . 115 6.2 Architecture of the Tukwila convergent query processor . 123 6.3 Experimental results over 100Mbps LAN . 129 6.4 Experimental results over slow network . 132 6.5 Performance of approach under limited memory . 133 7.1 Example of schema mediation in a PDMS . 140 7.2 Piazza system architecture . 141 iv LIST OF TABLES 4.1 Physical query operators and algorithms in Tukwila . 59 4.2 Experimental data sets . 67 4.3 Systems compared in Section 4.6.1. 68 4.4 List of pattern-matching queries . 68 4.5 List of queries used in XML processing experiments . 75 6.1 Data sources for experiments . 128 8.1 Comparison of adaptive query processing techniques . 157 v ACKNOWLEDGMENTS Portions of this dissertation have previously been published in SIGMOD [IFF+99] and in the IEEE Data Engineering Bulletin [IHW01, ILW+00]. However, these portions have been significantly revised and extended within this dissertation. Additionally, portions of Chapter 4 have been submitted concurrently to the VLDB Journal. It's amazing to look back and see how things have changed over the past few years, how others have influenced me. I've been blessed with a brilliant and incredibly generous group of collaborators and advisors, who've given me great ideas and shaped my research ideas and my thesis work. Special thanks to my advisors, Alon Halevy and Dan Weld, who let me be creative but kept me on track, and with whom I've had countless stimulating discussions that led to new ideas. Even more importantly, they taught me choose worthwhile problems and aim high. I have come to understand just how critical this is in the research world. Thanks also to Steve Gribble, Hank Levy, and Dan Suciu for showing me a broader perspective on my research topics — it really helps to see a problem from an outsider's perspective in many cases — and for many fruitful discussions and arguments. And I am greatly appreciative of the amount of work they put into preparing me for the interview circuit, despite the fact that I did not have a formal advisee relationship with them. I'm also grateful to Igor Tatarinov, Jayant Madhavan, Maya Rodrig, and Ste- fan Sariou for their contributions to the various projects in which I have partic- ipated these past few years. I greatly enjoyed their ideas and their enthusiasm, and I learned a great deal from working with them. Many of these people have also been invaluable sources of comments on my papers. A special thank-you is warranted for Rachel Pottinger, who has been a fellow “databaser” and constant source of encouragement since the beginning — and vi to Steve Wolfman as well, who, while not a database person, has been a good friend and source of feedback. They have been perhaps the best exemplars of why this department has a stellar reputation as a place to work. I'd also like to express my appreciation for those who contributed sugges- tions and feedback to my work, even if they weren't officially affiliated with it: Corin Anderson, Phil Bernstein, Luc Bouganim, Neal Cardwell, Andy Collins, AnHai Doan, Daniela Florescu, Dennis Lee, Hartmut Liefke, David Maier, Ioana Manolescu, Oren Zamir, and the anonymous reviewers of my conference and journal submissions.
Recommended publications
  • Evolution of Database Technology
    Introduction and Database Technology By EM Bakker September 11, 2012 Databases and Data Mining 1 DBDM Introduction Databases and Data Mining Projects at LIACS Biological and Medical Databases and Data Mining CMSB (Phenotype Genotype), DIAL CGH DB Cyttron: Visualization of the Cell GRID Computing VLe: Virtual Lab e-Science environments DAS3/DAS4 super computer Research on Fundamentals of Databases and Data Mining Database integration Data Mining algorithms Content Based Retrieval September 11, 2012 Databases and Data Mining 2 DBDM Databases (Chapters 1-7): The Evolution of Database Technology Data Preprocessing Data Warehouse (OLAP) & Data Cubes Data Cubes Computation Grand Challenges and State of the Art September 11, 2012 Databases and Data Mining 3 DBDM Data Mining (Chapters 8-11): Introduction and Overview of Data Mining Data Mining Basic Algorithms Mining data streams Mining Sequence Patterns Graph Mining September 11, 2012 Databases and Data Mining 4 DBDM Further Topics Mining object, spatial, multimedia, text and Web data Mining complex data objects Spatial and spatiotemporal data mining Multimedia data mining Text mining Web mining Applications and trends of data mining Mining business & biological data Visual data mining Data mining and society: Privacy-preserving data mining September 11, 2012 Databases and Data Mining 5 [R] Evolution of Database Technology September 11, 2012 Databases and Data Mining 6 Evolution of Database Technology 1960s: (Electronic) Data collection, database creation, IMS
    [Show full text]
  • Oracle Rdb Extension for OEM 9I Release V7.1.0.0
    Rdb-OEM Agent Installation Guide 7/16/03 2:02 PM Oracle Rdb Extension for OEM 9i Release V7.1.0.0 Oracle Rdb Extension for OEM 9i Rdb-OEM Installation Guide for Oracle Intelligent Agent Release 7.1.0.0 for Oracle Enterprise Managers on Windows NT, Windows 2000, Sun Solaris OS (SPARC) for Oracle Intelligent Agents on OpenVMS for Alpha June 2003 This readme provides information on how to install the Oracle Rdb Extension for the Oracle Intelligent Agent on OpenVMS for Alpha systems using the Oracle Rdb Server CD media. The Oracle Enterprise Manager 9i is a 3-tier management framework consisting of Oracle Enterprise Manager Console Oracle Management Server Oracle Intelligent Agent Together, they can be used to Administer the complete Oracle environment, including databases, iAS servers, applications, and services. Diagnose, modify, and tune multiple Oracle databases. Schedule tasks on multiple systems at varying time intervals. Monitor Oracle database conditions throughout the network. Administer multiple network nodes and services from many locations. Share tasks with other administrators. Group related services together to facilitate administration tasks. Launch integrated Oracle and third-party tools. In order to facilitate the management of Oracle Rdb databases through the management framework, an additional installation is required at each tier. Each of these additional installations are described in this readme. The top tier consists of the Oracle Enterprise Manager Console. The Console is a GUI that allows you to interface into the management framework. Via the Console, you may interact with the Oracle Management Server and the Oracle Intelligent Agent to perform all the functions listed above.
    [Show full text]
  • Connx 14.0 Release Notes October 7, 2019
    ConnX 14.0 Release Notes October 7, 2019 Software AG Table of Contents ConnX 14.0 Release Notes ................................................................................................ 3 Overview .......................................................................................................................... 3 ConnX Architecture on Windows .................................................................................... 4 ConnX Architecture on UNIX ........................................................................................... 5 ConnX Architecture (ODBC/JDBC/OLEDB/.NET Provider) ............................................... 6 ConnX Client Engine for Windows ................................................................................... 6 ConnX Client Engine for UNIX .......................................................................................... 6 ConnX Data Dictionary ..................................................................................................... 6 ConnX Server ................................................................................................................... 6 ConnX JDBC Thin Client ................................................................................................... 6 ConnX JDBC Server .......................................................................................................... 6 ConnX JDBC Router .......................................................................................................... 7 ConnX DataSync ..............................................................................................................
    [Show full text]
  • CMU 15-445/645 Database Systems (Fall 2018 :: Query Optimization
    Query Optimization Lecture #13 Database Systems Andy Pavlo 15-445/15-645 Computer Science Fall 2018 AP Carnegie Mellon Univ. 2 ADMINISTRIVIA Mid-term Exam is on Wednesday October 17th → See mid-term exam guide for more info. Project #2 – Checkpoint #2 is due Friday October 19th @ 11:59pm. CMU 15-445/645 (Fall 2018) 4 QUERY OPTIMIZATION Remember that SQL is declarative. → User tells the DBMS what answer they want, not how to get the answer. There can be a big difference in performance based on plan is used: → See last week: 1.3 hours vs. 0.45 seconds CMU 15-445/645 (Fall 2018) 5 IBM SYSTEM R First implementation of a query optimizer. People argued that the DBMS could never choose a query plan better than what a human could write. A lot of the concepts from System R’s optimizer are still used today. CMU 15-445/645 (Fall 2018) 6 QUERY OPTIMIZATION Heuristics / Rules → Rewrite the query to remove stupid / inefficient things. → Does not require a cost model. Cost-based Search → Use a cost model to evaluate multiple equivalent plans and pick the one with the lowest cost. CMU 15-445/645 (Fall 2018) 7 QUERY PLANNING OVERVIEW System Catalog Cost SQL Query Model Abstract Syntax Annotated Annotated Tree AST AST Parser Binder Rewriter Optimizer (Optional) Name→Internal ID Query Plan CMU 15-445/645 (Fall 2018) 8 TODAY'S AGENDA Relational Algebra Equivalences Plan Cost Estimation Plan Enumeration Nested Sub-queries Mid-Term Review CMU 15-445/645 (Fall 2018) 9 RELATIONAL ALGEBRA EQUIVALENCES Two relational algebra expressions are equivalent if they generate the same set of tuples.
    [Show full text]
  • Evolution of Database Technology  1960S:  (Electronic) Data Collection, Database Creation, IMS (Hierarchical Database System by IBM) and Network DBMS
    Database Technology Erwin M. Bakker & Stefan Manegold https://homepages.cwi.nl/~manegold/DBDM/ http://liacs.leidenuniv.nl/~bakkerem2/dbdm/ [email protected] [email protected] 9/21/18 Databases and Data Mining 1 Evolution of Database Technology 1960s: (Electronic) Data collection, database creation, IMS (hierarchical database system by IBM) and network DBMS 1970s: Relational data model, relational DBMS implementation 1980s: RDBMS, advanced data models (extended-relational, OO, deductive, etc.) Application-oriented DBMS (spatial, scientific, engineering, etc.) 9/21/18 Databases and Data Mining 2 Evolution of Database Technology 1990s: Data mining, data warehousing, multimedia databases, and Web databases 2000 - Stream data management and mining Data mining and its applications Web technology Data integration, XML Social Networks (Facebook, etc.) Cloud Computing global information systems Emerging in-house solutions In Memory Databases Big Data 9/21/18 Databases and Data Mining 3 1960’s Companies began automating their back-office bookkeeping in the 1960s COBOL and its record-oriented file model were the work-horses of this effort Typical work-cycle: 1. a batch of transactions was applied to the old-tape-master 2. a new-tape-master produced 3. printout for the next business day. COmmon Business-Oriented Language (COBOL 2002 standard) 9/21/18 Databases and Data Mining 4 COBOL A quote by Prof. dr. E.W. Dijkstra (Turing Award 1972) 18 June 1975: “The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offence.” September 2015: 9/21/18 Databases and Data Mining 5 COBOL Code (just an example!) 01 LOAN-WORK-AREA.
    [Show full text]
  • Oracle Rdb7™ Guide to Using the Oracle SQL/Services™ Client API
    Oracle Rdb7™ Guide to Using the Oracle SQL/Services™ Client API Release 7.0 Part No. A41981-1 ® Guide to Using the Oracle SQL/Services Client API Release 7.0 Part No. A41981-1 Copyright © 1993, 1996, Oracle Corporation. All rights reserved. This software contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Restricted Rights Legend Programs delivered subject to the DOD FAR Supplement are ’commercial computer software’ and use, duplication and disclosure of the programs shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are ’restricted computer software’ and use, duplication and disclosure of the programs shall be subject to the restrictions in FAR 52.227-14, Rights in Data—General, including Alternate III (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee’s responsibility to take all appropriate fail-safe, back up, redundancy and other measures to ensure the safe use of such applications if the programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the programs.
    [Show full text]
  • Políticas De Soporte Técnico De Software De Oracle
    Políticas de Soporte Técnico de Software de Oracle Fecha de Entrada en Vigencia: 02 de abril de 2021 Oracle Software Technical Support Policies: 02-April-2021 Página 1 de 42 Contenido 1. Descripción general 4 2. Términos del Soporte 4 Tarifas de Soporte Técnico 4 Período de Soporte 5 Conjunto de Licencias 5 Niveles de Servicio Equivalentes 6 Reinstalación del Soporte Técnico de Oracle 6 Fijación de Precios después de la Reducción de Licencias o del Nivel de Soporte 7 Paquetes de Aplicaciones Personalizados 7 Programas Sin Soporte 7 Contactos Técnicos 8 Actualizaciones de Programas 8 3. Soporte De Por Vida 9 4. Niveles de Soporte Técnico de Oracle 13 Licencia de Actualización de Programas y Soporte 13 Soporte Extendido 15 Soporte de Mantenimiento 16 Soporte Premier y de Mantenimiento para el Software de Oracle Communications Network 19 Soporte de Software y Soporte de Mantenimiento para Oracle Communications Network 20 5. Servicios de Soporte Adicionales Disponibles para la Compra 22 Paquete de Soporte para Incidentes en el Servidor 22 Soporte para Herramientas de Desarrollo Oracle Java 23 Soporte para Herramientas de Oracle Developer Studio 23 Soporte para Oracle Application Development Framework Essentials 23 Soporte para Java SE y Soporte para Java SE para Proveedores de Software Independientes 24 Soporte de Desarrollo para Oracle Java Embedded y Soporte de Desarrollo para Oracle Java Embedded Suite 24 Soporte para Oracle Solaris 10 Container 25 Soporte para NoSQL Database Community Edition 25 Paquetes de Solicitudes de Servicio 25
    [Show full text]
  • IBM Cloudant: Database As a Service Fundamentals
    Front cover IBM Cloudant: Database as a Service Fundamentals Understand the basics of NoSQL document data stores Access and work with the Cloudant API Work programmatically with Cloudant data Christopher Bienko Marina Greenstein Stephen E Holt Richard T Phillips ibm.com/redbooks Redpaper Contents Notices . 5 Trademarks . 6 Preface . 7 Authors. 7 Now you can become a published author, too! . 8 Comments welcome. 8 Stay connected to IBM Redbooks . 9 Chapter 1. Survey of the database landscape . 1 1.1 The fundamentals and evolution of relational databases . 2 1.1.1 The relational model . 2 1.1.2 The CAP Theorem . 4 1.2 The NoSQL paradigm . 5 1.2.1 ACID versus BASE systems . 7 1.2.2 What is NoSQL? . 8 1.2.3 NoSQL database landscape . 9 1.2.4 JSON and schema-less model . 11 Chapter 2. Build more, grow more, and sleep more with IBM Cloudant . 13 2.1 Business value . 15 2.2 Solution overview . 16 2.3 Solution architecture . 18 2.4 Usage scenarios . 20 2.5 Intuitively interact with data using Cloudant Dashboard . 21 2.5.1 Editing JSON documents using Cloudant Dashboard . 22 2.5.2 Configuring access permissions and replication jobs within Cloudant Dashboard. 24 2.6 A continuum of services working together on cloud . 25 2.6.1 Provisioning an analytics warehouse with IBM dashDB . 26 2.6.2 Data refinement services on-premises. 30 2.6.3 Data refinement services on the cloud. 30 2.6.4 Hybrid clouds: Data refinement across on/off–premises. 31 Chapter 3.
    [Show full text]
  • 15-445/645 Database Systems (Fall 2020) Carnegie Mellon University Prof
    Lecture #02: Intermediate SQL 15-445/645 Database Systems (Fall 2020) https://15445.courses.cs.cmu.edu/fall2020/ Carnegie Mellon University Prof. Andy Pavlo 1 Relational Languages Edgar Codd published a major paper on relational models in the early 1970s. Originally, he only defined the mathematical notation for how a DBMS could execute queries on a relational model DBMS. The user only needs to specify the result that they want using a declarative language (i.e., SQL). The DBMS is responsible for determining the most efficient plan to produce that answer. Relational algebra is based on sets (unordered, no duplicates). SQL is based on bags (unordered, allows duplicates). 2 SQL History Declarative query lanaguage for relational databases. It was originally developed in the 1970s as part of the IBM System R project. IBM originally called it “SEQUEL” (Structured English Query Language). The name changed in the 1980s to just “SQL” (Structured Query Language). The language is comprised of different classes of commands: 1. Data Manipulation Language (DML): SELECT, INSERT, UPDATE, and DELETE statements. 2. Data Definition Language (DDL): Schema definitions for tables, indexes, views, and other objects. 3. Data Control Language (DCL): Security, access controls. SQL is not a dead language. It is being updated with new features every couple of years. SQL-92 is the minimum that a DBMS has to support to claim they support SQL. Each vendor follows the standard to a certain degree but there are many proprietary extensions. 3 Aggregates An aggregation function takes in a bag of tuples as its input and then produces a single scalar value as its output.
    [Show full text]
  • Oracle® Rdb Developer Tools for Visual Studio Release Notes Release 7.3.5.0.0 July 2016
    Oracle® Rdb Developer Tools for Visual Studio Release Notes Release 7.3.5.0.0 July 2016 Oracle Rdb Developer Tools for Visual Studio, Release 7.3.5.0.0. Copyright © 2011, 2016 Oracle and/or its affiliates. All rights reserved. Primary Author: Jim Murray. Contributing Author: Contributor: This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Oracle® Rdb Developer Tools For
    Oracle® Rdb Connectivity Management Release Notes Release 7.3.0.0 May 2014 Oracle Rdb Connectivity Management, Release 7.3 Copyright © 2014 Oracle Corporation. All rights reserved. Primary Author: Jim Murray. Contributing Author: Contributors : This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Oracle Corporation
    ORACLE CORPORATION The Oracle Corporation is an American global computer technology corporation, headquartered in Redwood City, California. The company primarily specializes in developing and marketing computer hardware systems and enterprise software products – particularly its own brands of database management systems. In 2011 Oracle was the second- largest software maker by revenue, after Microsoft.[3] The company also develops and builds tools for database development and systems of middle-tier software, enterprise resource planning (ERP) software, customer relationship management (CRM) software and supply chain management (SCM) software. Larry Ellison, a co-founder of Oracle, served as Oracle's CEO from founding. On September 18, 2014, it was announced that he would be stepping down (with Mark Hurd and Safra Catz to become CEOs). Ellison became executive chairman and CTO.[4] He also served as the Chairman of the Board until his replacement by Jeffrey O. Henley in 2004. On August 22, 2008, the Associated Press ranked Ellison as the top-paid chief executive in the world.[5] Larry Ellison , Ellison was born in New York City but grew up in Chicago. He studied at the University of Illinois at Urbana–Champaign and the University of Chicago without graduating before moving to California in 1966. While working at Ampex in the early 1970s, he became influenced by Edgar F. Codd's research on relational database design, which led in 1977 to the formation of what became Oracle. Oracle became a successful database vendor to mid- and low- Larry Ellison in October 2009. range systems, competing with Sybase and Microsoft SQL Server, Born August 17, 1944 (age 71) which led to Ellison being listed by Forbes Lower East Side, Manhattan, New York, U.S.
    [Show full text]