Oracle® SQL Developer Data Modeler User's Guide

Total Page:16

File Type:pdf, Size:1020Kb

Oracle® SQL Developer Data Modeler User's Guide Oracle® SQL Developer Data Modeler User's Guide Release 17.4 E92382-01 December 2017 Oracle SQL Developer Data Modeler User's Guide, Release 17.4 E92382-01 Copyright © 2008, 2017, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov 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, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle. Contents Preface Audience xii Documentation Accessibility xii Product Accessibility xii Related Documents xii Conventions xiii Third-Party License Information xiii 1 Data Modeler Concepts and Usage 1.1 Installing and Getting Started with SQL Developer Data Modeler 1-1 1.2 Data Modeler User Interface 1-2 1.2.1 Menus for Data Modeler 1-4 1.2.2 Context Menus 1-8 1.3 Working with Data Modeler 1-10 1.3.1 Database Design 1-11 1.3.2 Data Types Model 1-11 1.3.2.1 Data Types Diagram and Subviews 1-12 1.3.2.2 Distinct Types 1-13 1.3.2.3 Structured Types 1-14 1.3.2.4 Collection Types 1-14 1.3.2.5 Logical Types 1-14 1.3.3 Process Model 1-15 1.3.3.1 Data Flow Diagrams 1-16 1.3.3.2 Transformation Processes and Packages 1-16 1.3.4 Logical Model 1-16 1.3.4.1 Logical Diagram and Subviews 1-17 1.3.4.2 Entities 1-18 1.3.4.3 Attributes 1-18 1.3.4.4 Unique Identifiers (UIDs) 1-18 1.3.4.5 Inheritances 1-18 1.3.4.6 Relations 1-18 1.3.4.7 Arcs 1-19 iii 1.3.4.8 Type Substitution 1-19 1.3.4.9 Views 1-19 1.3.5 Relational Models 1-19 1.3.5.1 Relational Diagram and Subviews 1-20 1.3.5.2 Tables 1-21 1.3.5.3 Columns 1-21 1.3.5.4 Indexes 1-21 1.3.5.5 Relations 1-21 1.3.5.6 Relational Views 1-21 1.3.6 Physical Models 1-22 1.3.6.1 Clusters 1-22 1.3.6.2 Contexts 1-23 1.3.6.3 Dimensions 1-23 1.3.6.4 Directories 1-23 1.3.6.5 Disk Groups 1-23 1.3.6.6 External Tables 1-23 1.3.6.7 Indexes 1-23 1.3.6.8 Roles 1-23 1.3.6.9 Rollback Segments 1-24 1.3.6.10 Segments (Segment Templates) 1-24 1.3.6.11 Sequences 1-24 1.3.6.12 Snapshots 1-24 1.3.6.13 Stored Procedures 1-24 1.3.6.14 Synonyms 1-24 1.3.6.15 Structured Types 1-24 1.3.6.16 Tables 1-25 1.3.6.17 Tablespaces 1-25 1.3.6.18 Users 1-25 1.3.6.19 Views 1-25 1.3.7 Business Information 1-25 1.3.7.1 Contacts 1-26 1.3.7.2 Documents 1-26 1.3.7.3 Emails 1-26 1.3.7.4 Locations 1-26 1.3.7.5 Resource Locators 1-26 1.3.7.6 Responsible Parties 1-27 1.3.7.7 Telephones 1-27 1.4 Approaches to Data Modeling 1-27 1.4.1 Top-Down Modeling 1-27 1.4.2 Bottom-Up Modeling 1-29 1.4.3 Targeted Modeling 1-30 iv 1.5 User Preferences for Data Modeler 1-31 1.5.1 Environment 1-31 1.5.2 Data Modeler 1-32 1.5.2.1 DDL 1-33 1.5.2.2 Diagram 1-36 1.5.2.3 Model 1-36 1.5.2.4 Reports 1-39 1.5.2.5 Search 1-40 1.5.2.6 Third Party JDBC Drivers 1-40 1.5.3 Format 1-40 1.5.4 Global Ignore List 1-41 1.5.5 Mouse Actions 1-41 1.5.6 Shortcut Keys (Accelerator Keys) 1-42 1.5.7 SSH (Secure Shell) 1-43 1.5.8 Usage Reporting 1-43 1.5.9 Versioning 1-43 1.5.10 Web Browser and Proxy 1-44 1.6 Saving, Opening, Exporting, and Importing Designs 1-45 1.6.1 Importing a DDL File 1-46 1.6.2 Importing Cube Views Metadata 1-46 1.6.3 Importing from Microsoft XMLA 1-46 1.6.4 Importing an ERwin File 1-46 1.6.5 Importing from a Data Dictionary 1-47 1.6.6 Importing an Oracle Designer Model 1-47 1.6.7 Importing a Data Modeler Design 1-47 1.6.8 Importing a Domain 1-47 1.7 Exporting and Importing Preferences and Other Settings 1-47 1.7.1 Restoring the Original Data Modeler Preferences 1-48 1.8 Data Modeler Reports 1-48 1.8.1 Generating Reports as RTF, HTML, or PDF Files 1-48 1.8.2 Using the Reporting Repository and Reporting Schema 1-50 1.8.3 Using SQL Developer to View Exported Reporting Schema Data 1-51 1.8.3.1 Design Content reports 1-52 1.8.3.2 Design Rules reports 1-52 1.9 Using Versioning 1-53 1.9.1 About Subversion and Data Modeler 1-53 1.9.1.1 Pending Changes 1-53 1.9.2 Basic Workflow: Using Subversion with a Design 1-54 1.10 Data Modeler Accessibility Information 1-55 1.11 For More Information About Data Modeling 1-56 v 2 Data Modeler Tutorial: Modeling for a Small Database 2.1 Develop the Logical Model 2-1 2.1.1 Adding Domains 2-1 2.1.2 Creating the Books Entity 2-2 2.1.3 Creating the Patrons Entity 2-3 2.1.4 Creating the Transactions Entity 2-4 2.1.5 Creating Relations Between Entities 2-5 2.2 Develop the Relational Model 2-6 2.3 Generate DDL 2-6 2.4 Save the Design 2-7 3 Data Modeler Dialog Boxes 3.1 Add Event 3-1 3.2 Add/Remove Objects 3-1 3.3 Advanced Properties (Connections) 3-2 3.4 Arc Properties 3-2 3.5 Attribute Properties 3-3 3.6 Change Subview Object Names Prefix 3-4 3.7 Change Request Properties 3-4 3.8 Change Requests Administration 3-5 3.9 Check for Updates 3-5 3.10 Choose Directory 3-6 3.11 Collection Type Properties 3-6 3.12 Column Properties 3-7 3.13 Common Information in Dialog Boxes 3-9 3.14 Compare Mapping 3-10 3.15 Compare Modeling Designs 3-10 3.16 Compare Models 3-10 3.17 Color Palette and Custom Colors 3-12 3.18 Connection Information 3-12 3.19 Contact Properties 3-12 3.20 Create Database Connection 3-13 3.21 Create Discovered Foreign Keys 3-14 3.22 Cube Properties 3-15 3.23 Custom Reports Template 3-17 3.24 Data Dictionary Connections 3-18 3.25 Data Dictionary Import (Metadata Extraction) 3-19 3.26 Database Connection Editor 3-20 3.27 DDL File Editor 3-20 3.28 DDL Generation Options 3-21 vi 3.29 Design Properties 3-22 3.30 Design Rules 3-24 3.30.1 Design Rules 3-24 3.30.2 Custom Rules 3-25 3.30.3 Libraries 3-26 3.30.4 Transformations 3-26 3.31 Dimension Properties 3-26 3.32 Display Properties 3-28 3.33 Distinct Type Properties 3-28 3.34 Document Properties 3-28 3.35 Domain Properties (Domains Model) 3-29 3.36 Domains Administration 3-29 3.37 Email Properties 3-30 3.38 Engineering 3-30 3.39 Entity Properties 3-32 3.40 Event Properties 3-34 3.41 Export Cube Views Metadata 3-35 3.42 Export to Microsoft XMLA 3-35 3.43 Export to Oracle Analytic Workspaces 3-35 3.44 Export to Reporting Schema 3-36 3.45 Export Wizard 3-37 3.46 Export/Import Connections 3-38 3.46.1 Export Connections 3-38 3.46.2 Import Connections 3-39 3.47 External Agent Properties 3-39 3.48 External Data Properties 3-41 3.49 File Processing 3-41 3.50 Find Object (Search) 3-41 3.51 Flow Properties 3-42 3.52 Foreign Key Properties 3-43 3.53 Glossary Editor 3-44 3.54 Hierarchy Properties 3-46 3.55 Import Domains 3-47 3.56 Import Glossary (Naming Standard Definitions) 3-47 3.57 Import Mapped Models from VAR Files 3-48 3.58
Recommended publications
  • Powerdesigner 16.6 Data Modeling
    SAP® PowerDesigner® Document Version: 16.6 – 2016-02-22 Data Modeling Content 1 Building Data Models ...........................................................8 1.1 Getting Started with Data Modeling...................................................8 Conceptual Data Models........................................................8 Logical Data Models...........................................................9 Physical Data Models..........................................................9 Creating a Data Model.........................................................10 Customizing your Modeling Environment........................................... 15 1.2 Conceptual and Logical Diagrams...................................................26 Supported CDM/LDM Notations.................................................27 Conceptual Diagrams.........................................................31 Logical Diagrams............................................................43 Data Items (CDM)............................................................47 Entities (CDM/LDM)..........................................................49 Attributes (CDM/LDM)........................................................55 Identifiers (CDM/LDM)........................................................58 Relationships (CDM/LDM)..................................................... 59 Associations and Association Links (CDM)..........................................70 Inheritances (CDM/LDM)......................................................77 1.3 Physical Diagrams..............................................................82
    [Show full text]
  • Data Modeler User's Guide
    Oracle® SQL Developer Data Modeler User's Guide Release 18.1 E94838-01 March 2018 Oracle SQL Developer Data Modeler User's Guide, Release 18.1 E94838-01 Copyright © 2008, 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov 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, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Relational and Object-Oriented Databases
    Relational and Object-Oriented Databases by Willi-Hans Steeb International School for Scientific Computing Contents 1 What is a table? 1 1.1 Introduction . 1 1.2 Examples . 5 1.3 Tables in Programs . 8 1.4 Table and Relation . 33 2 Structured Query Language 35 2.1 Introduction . 35 2.2 Integrity Rules . 38 2.3 SQL Commands . 39 2.3.1 Introduction . 39 2.3.2 Aggregate Function . 40 2.3.3 Arithmetic Operators . 40 2.3.4 Logical Operators . 40 2.3.5 SELECT Statement . 41 2.3.6 INSERT Command . 45 2.3.7 DELETE Command . 46 2.3.8 UPDATE Command . 47 2.3.9 CREATE TABLE Command . 48 2.3.10 DROP TABLE Command . 51 2.3.11 ALTER TABLE Command . 52 2.4 Set Operators . 53 2.5 Views . 60 2.6 Primary and Foreign Keys . 62 2.7 Datatypes in SQL . 63 2.8 Joins . 66 2.9 Stored Procedure . 71 2.10 MySQL Commands . 72 2.11 Cursors . 73 2.12 PL and SQL . 75 2.13 ABAP/4 and SQL . 76 2.14 Query Processing and Optimization . 77 i 3 Normal Forms 83 3.1 Introduction . 83 3.2 Anomalies . 87 3.3 Example . 89 3.4 Fourth and Fifth Normal Forms . 93 4 Transaction 101 4.1 Introduction . 101 4.2 Data Replication . 107 4.3 Locks . 108 4.4 Deadlocking . 111 4.5 Threads . 117 4.5.1 Introduction . 117 4.5.2 Thread Class . 119 4.5.3 Example . 121 4.5.4 Priorities . 123 4.5.5 Synchronization and Locks .
    [Show full text]
  • SQL Developer Data Modeler: a Top-Down Product Overview
    SQL Developer Data Modeler: A Top-Down Product Overview Sue Harper Oracle United Kingdom Keywords: SQL Developer Data Modeler, ERD, DDL Generation, model, capture, design Introduction Oracle SQL Developer Data Modeler is a graphical data modeling tool for creating, browsing and editing data models, including logical, relational, physical, multi-dimensional, and data type models. It supports forward and reverse engineering from Oracle Database, Microsoft SQL Server and IBM DB2 databases and the generation of DDL scripts for these databases. SQL Developer Data Modeler offers features and utilities that enhance the data modeling experience, improve productivity and promote the use of standards. SQL Developer Data Modeler is designed for a broad spectrum of database developers; from business architects to DBAs and from database to application developers, serving as a powerful communication tool between developers and business users. In this article we review the main modelers and features in SQL Developer Data Modeler 2.0 starting with the logical model and progressing through the features to the final DDL script. Often called the top-down approach, this is not the only flow of work through the product, as indeed, users can start by importing a data model and reverse engineering the objects to create an initial diagram and progressing from there. We will refer to various methods of creating models and updating the database using the product. Integrated Models SQL Developer Data Modeler provides facilities to build sets of related and integrated models. Many consider the core of SQL Developer Data Modeler to be the logical model. It is this logical model that provides a true implementation-independent view of enterprise information.
    [Show full text]
  • An Introduction to Oracle SQL Developer Data Modeler
    An Oracle White Paper June 2009 An Introduction to Oracle SQL Developer Data Modeler Oracle White Paper— An Introduction to Oracle SQL Developer Data Modeler Introduction ....................................................................................... 1 Oracle SQL Developer Data Modeler ................................................ 2 Architecture ................................................................................... 2 Integrated Models.............................................................................. 4 Logical Models .............................................................................. 4 Relational Models.......................................................................... 5 Physical Models............................................................................. 5 Multi-dimensional Models .............................................................. 7 Data Type and Structured Type Models ...................................... 10 Spatial Models............................................................................. 11 Creating Models .............................................................................. 13 Creating New Models .................................................................. 13 Importing from the Data Dictionary .............................................. 13 Importing from Oracle Designer................................................... 14 Generating Scripts........................................................................... 15 Generating DDL
    [Show full text]
  • Handling Unstructured Data Type in DB2 and Oracle
    Communications of the IIMA Volume 3 Issue 2 Article 6 2003 Handling Unstructured Data Type in DB2 and Oracle Alexander P. Pons Computer Information Systems, University of Miami Hassan Aljifri Computer Information Systems, University of Miami Follow this and additional works at: https://scholarworks.lib.csusb.edu/ciima Recommended Citation Pons, Alexander P. and Aljifri, Hassan (2003) "Handling Unstructured Data Type in DB2 and Oracle," Communications of the IIMA: Vol. 3 : Iss. 2 , Article 6. Available at: https://scholarworks.lib.csusb.edu/ciima/vol3/iss2/6 This Article is brought to you for free and open access by CSUSB ScholarWorks. It has been accepted for inclusion in Communications of the IIMA by an authorized editor of CSUSB ScholarWorks. For more information, please contact [email protected]. Alexander P. Pons, Hassan Aljifri Handling Unstructured Data Type in DB2 and Oracle Alexander P. Pons Computer Information Systems, University of Miami, 421 Jenkins Building, Coral Gables, FL 33146 Phone: 305-284-1960, Fax: 305-284-5161, [email protected] Hassan Aljifri Computer Information Systems, University of Miami, 421 Jenkins Building, Coral Gables, FL 33146 Phone: 305-284-4767, Fax: 305-284-5161, [email protected] ABSTRACT The objective of our work is to determine which mainstream object-relational database management systems (ORDMS) provide convenient facilities for the storage and manipulation of unstructured data objects. These objects, which consist of video, audio, photographs, and even executable code such as Java applets, are becoming readily employed by desktop, network, and Internet applications. Typically, these ORDMSs must store the objects in a manner by which they can be easily accessed, but more importantly, easily processed during either storage or retrieval.
    [Show full text]
  • Oracle® SQL Developer Data Modeler User's Guide
    Oracle® SQL Developer Data Modeler User's Guide Release 17.3 E90546-01 September 2017 Oracle SQL Developer Data Modeler User's Guide, Release 17.3 E90546-01 Copyright © 2008, 2017, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov 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, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • 25 Object-Database Systems
    25 OBJECT-DATABASESYSTEMS with Joseph M. Hellerstein U. C. Berkeley You know my methods, Watson. Apply them. —Arthur Conan Doyle, The Memoirs of Sherlock Holmes Relational database systems support a small, fixed collection of data types (e.g., in- tegers, dates, strings), which has proven adequate for traditional application domains such as administrative data processing. In many application domains, however, much more complex kinds of data must be handled. Typically this complex data has been stored in OS file systems or specialized data structures, rather than in a DBMS. Ex- amples of domains with complex data include computer-aided design and modeling (CAD/CAM), multimedia repositories, and document management. As the amount of data grows, the many features offered by a DBMS—for example, reduced application development time, concurrency control and recovery, indexing support, and query capabilities—become increasingly attractive and, ultimately, nec- essary. In order to support such applications, a DBMS must support complex data types. Object-oriented concepts have strongly influenced efforts to enhance database support for complex data and have led to the development of object-database systems, which we discuss in this chapter. Object-database systems have developed along two distinct paths: Object-oriented database systems: Object-oriented database systems are proposed as an alternative to relational systems and are aimed at application domains where complex objects play a central role. The approach is heavily in- fluenced by object-oriented programming languages and can be understood as an attempt to add DBMS functionality to a programming language environment. Object-relational database systems: Object-relational database systems can be thought of as an attempt to extend relational database systems with the func- tionality necessary to support a broader class of applications and, in many ways, provide a bridge between the relational and object-oriented paradigms.
    [Show full text]
  • Oracle to DB2 Conversion Guide: Compatibility Made Easy
    Front cover IBM® Information Management Software Oracle to DB2 Conversion Guide: Compatibility Made Easy Move Oracle to DB2 efficiently and effectively Learn about DB2 10.5 Oracle Database compatibility features Use Oracle PL/SQL skills directly with DB2 10.5 Yvonne Chan Nick Ivanov Olaf Mueller ibm.com/redbooks International Technical Support Organization Oracle to DB2 Conversion Guide: Compatibility Made Easy September 2013 SG24-7736-02 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. Third Edition (September 2013) This edition applies to IBM DB2 for Linux, UNIX, and Windows Version 10.5. © Copyright International Business Machines Corporation 2009, 2013. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . x Preface . xi Authors . xii Acknowledgements . xiii Now you can become a published author, too! . xiv Comments welcome. xiv Stay connected to IBM Redbooks publications . xv Summary of changes . xvii September 2013, Third Edition. xvii Chapter 1. Introduction. 1 1.1 DB2 family of products . 2 1.1.1 DB2 editions . 2 1.1.2 IBM DB2 10.5 Advanced Enterprise Edition features . 6 1.1.3 DB2 10 autonomic computing features . 7 1.1.4 Introduction to PureData . 9 1.2 DB2 Oracle database compatibility features overview . 9 1.2.1 Concurrency control . 10 1.2.2 Data types . 11 1.2.3 Implicit casting. 11 1.2.4 SQL Standard . 12 1.2.5 PL/SQL . 12 1.2.6 Built-in packages.
    [Show full text]
  • ISG STAFF WORKING PAPERS Objects in the Database
    soG ISG STAFF WORKING PAPERS Public Disclosure Authorized Public Disclosure Authorized Public Disclosure Authorized Objects in the Database: A Reality Check Parvez Bashir Information Public Disclosure Authorized Officer, ISGEC IFl - I Sol Grion ISG STAFF WORKING PAPERS ISG Staff Working Papers are reviewed by the VP-CIO and by the ISG Senior Management Team. Papers are evaluated and the best of the papers will be recognized. The series is envisioned to be forward-looking and cover a broad range of topics. Over a period of time, the papers will be compiled and published as a book. ffMy= .I Parvez Bashir Information Officer, ISGEC Objects in the Database: A Reality Check The RDBMS (Relational Database Management System) ruled the database roost in the 1980s and 00 (Object Oriented) programming languages revolutionized software development in the 1990s. RDBMSs and 00 programming languages have complementary strengths. Relational database systems are good for managing large amounts of data; object oriented programming languages are good at expressing complex relationships among objects. Relational database systems are good for data retrieval but provide little support for data manipulation; object oriented programming languages are excellent at data manipulation but provide little or no support for data persistence and retrieval. These complementary strengths have given birth to a new breed of database management systems popularly known as Object Relational Database Management Systems (ORDBMS). The other database model which deals purely with objects is the ODBMS (Object Database Management System). ODBMSs pre-date the object relational model and have been in use since time immemorial in niche applications including multimedia.
    [Show full text]
  • Programming Server Applications
    IBM® DB2 Universal Database™ Application Development Guide: Programming Server Applications Ve r s i o n 8 SC09-4827-00 IBM® DB2 Universal Database™ Application Development Guide: Programming Server Applications Ve r s i o n 8 SC09-4827-00 Before using this information and the product it supports, be sure to read the general information under Notices. This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. v To order publications online, go to the IBM Publications Center at www.ibm.com/shop/publications/order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at www.ibm.com/planetwide To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1993 - 2002. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About This Book ..........vii Chapter 3. SQL-Bodied Routines ....59 CREATE Statements for SQL-Bodied Routines 59 Part 1. Routines (Stored Dynamic SQL in SQL-Bodied Routines .
    [Show full text]
  • Data Movement Utilities Guide and Reference
    IBM® DB2 Universal Database™ Data Movement Utilities Guide and Reference Ve r s i o n 8 SC09-4830-00 IBM® DB2 Universal Database™ Data Movement Utilities Guide and Reference Ve r s i o n 8 SC09-4830-00 Before using this information and the product it supports, be sure to read the general information under Notices. This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this manual should not be interpreted as such. You can order IBM publications online or through your local IBM representative. v To order publications online, go to the IBM Publications Center at www.ibm.com/shop/publications/order v To find your local IBM representative, go to the IBM Directory of Worldwide Contacts at www.ibm.com/planetwide To order DB2 publications from DB2 Marketing and Sales in the United States or Canada, call 1-800-IBM-4YOU (426-4968). When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1999, 2002. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About This Book ..........vii Parallelism and Loading .......110 Who Should Use this Book .......vii Privileges, Authorities, and Authorizations How this Book is Structured ......vii Required to Use Load ........111 Using Load ............112 Chapter 1.
    [Show full text]