DOCSLIB.ORG

(DDL) Reference Manual

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
(DDL) Reference Manual Data Definition Language (DDL) Reference Manual Abstract This publication describes the DDL language syntax and the DDL dictionary database. The audience includes application programmers and database administrators. Product Version DDL D40 DDL H01 Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all subsequent H-series RVUs, and G06.26 and all subsequent G-series RVUs, until otherwise indicated by its replacement publications. Part Number Published 529431-003 May 2010 Document History Part Number Product Version Published 529431-002 DDL D40, DDL H01 July 2005 529431-003 DDL D40, DDL H01 May 2010 Legal Notices Copyright 2010 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Export of the information contained in this publication may require authorization from the U.S. Department of Commerce. Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation. Intel, Itanium, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java is a U.S. trademark of Sun Microsystems, Inc. Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks and IT DialTone and The Open Group are trademarks of The Open Group in the U.S. and other countries. Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. OSF shall not be liable for errors contained herein or for incidental consequential damages in connection with the furnishing, performance, or use of this material. © 1990, 1991, 1992, 1993 Open Software Foundation, Inc. This documentation and the software to which it relates are derived in part from materials supplied by the following: © 1987, 1988, 1989 Carnegie-Mellon University. © 1989, 1990, 1991 Digital Equipment Corporation. © 1985, 1988, 1989, 1990 Encore Computer Corporation. © 1988 Free Software Foundation, Inc. © 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. © 1985, 1987, 1988, 1989, 1990, 1991, 1992 International Business Machines Corporation. © 1988, 1989 Massachusetts Institute of Technology. © 1988, 1989, 1990 Mentat Inc. © 1988 Microsoft Corporation. © 1987, 1988, 1989, 1990, 1991, 1992 SecureWare, Inc. © 1990, 1991 Siemens Nixdorf Informationssysteme AG. © 1986, 1989, 1996, 1997 Sun Microsystems, Inc. © 1989, 1990, 1991 Transarc Corporation. This software and documentation are based in part on the Fourth Berkeley Software Distribution under license from The Regents of the University of California. OSF acknowledges the following individuals and institutions for their role in its development: Kenneth C.R.C. Arnold, Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980, 1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California. Printed in the US Data Definition Language (DDL) Reference Manual Glossary Index Examples Figures Tables Legal Notices What’s New in This Manual xix Manual Information xix New and Changed Information xix About This Manual xxi Audience xxii Prerequisite Manuals xxii Related Manuals xxiii Notation Conventions xxiii 1. Introduction to DDL Compiling and Translating Data Definitions 1-3 Using DDL Definitions 1-4 Creating a Dictionary 1-5 Creating a Database 1-7 Generating Source Code 1-9 Maintaining a Dictionary 1-12 Examining a Dictionary 1-14 2. DDL Language Elements Names 2-1 Syntax 2-2 Restrictions 2-2 File Names 2-3 Local File Names 2-3 Network File Names 2-4 Locale Names 2-4 Numbers 2-5 Strings 2-5 National Literals 2-6 Keywords 2-6 Hewlett-Packard Company—529431-003 i Contents 2. DDL Language Elements (continued) 2. DDL Language Elements (continued) Reserved Words 2-11 Special Characters 2-12 Comments 2-12 Dictionary Comments 2-13 Compiler Listing Comments 2-15 Statements 2-16 Commands 2-18 3. Running the DDL Compiler RUN DDL Command 3-1 Running the DDL Compiler Noninteractively 3-3 Running the DDL Compiler Interactively 3-4 Completion Codes 3-5 4. Named Constants CONSTANT 4-1 Numeric Constants 4-3 Product Version Constants 4-4 Existing Constants 4-5 C 4-5 COBOL 4-6 Pascal (D-series Systems Only) 4-6 TACL 4-7 TAL 4-8 Examples 4-8 Standard SPI Constants 4-9 5. Definitions and Records DEFINITION 5-1 Order of Clauses 5-2 Definition Length 5-2 Field Definition 5-4 Group Definition 5-5 Reference Definition 5-7 Error Handling 5-8 RECORD 5-8 File-Creation Syntax 5-10 Creation-Attribute Syntax 5-12 Record Structure Syntax 5-15 Data Definition Language (DDL) Reference Manual—529431-003 ii Contents 5. Definitions and Records (continued) 5. Definitions and Records (continued) Record Reference Syntax 5-16 Key Assignment Syntax 5-17 Error Handling 5-18 Examples 5-19 Syntax Elements 5-21 Clauses 5-21 Other Elements 5-23 6. Definition Attributes AS 6-3 DISPLAY 6-4 EDIT-PIC 6-5 EXTERNAL 6-6 FILLER 6-7 HEADING 6-9 HELP 6-10 JUSTIFIED 6-11 KEYTAG 6-12 LN 6-13 MUST BE 6-15 NULL 6-19 OCCURS 6-20 OCCURS DEPENDING ON 6-23 PICTURE 6-25 National Data Items 6-28 C 6-28 COBOL 6-29 FORTRAN 6-30 Pascal (D-series Systems Only) 6-30 pTAL and TAL 6-30 TACL 6-31 REDEFINES 6-31 C 6-32 COBOL 6-33 FORTRAN 6-33 Pascal (D-series Systems Only) 6-34 pTAL or TAL 6-35 TACL 6-36 Data Definition Language (DDL) Reference Manual—529431-003 iii Contents 6. Definition Attributes (continued) 6. Definition Attributes (continued) SPI-NULL 6-37 SQLNULLABLE 6-39 TACL 6-44 TYPE 6-48 Specifying TYPE data-type 6-51 Specifying TYPE def-name 6-66 Specifying TYPE * 6-67 UPSHIFT 6-69 USAGE 6-70 VALUE 6-75 66 RENAMES 6-79 88 Condition-Name 6-81 89 Enumeration 6-84 7. SPI Tokens Defining SPI Tokens 7-2 TOKEN-TYPE 7-2 TOKEN-TYPE Statement Output 7-5 Standard SPI TOKEN-TYPE Definitions 7-5 TOKEN-CODE 7-8 TOKEN-CODE Statement Output 7-10 Standard SPI TOKEN-CODE Definitions 7-10 TOKEN-MAP 7-13 Product Versions for Bit Fields 7-17 TOKEN-MAP Statement Output 7-18 Standard SPI Definitions in Token-Map Definitions 7-19 8. Dictionary-Manipulation Statements DELETE 8-1 EXIT 8-4 OUTPUT 8-5 OUTPUT UPDATE 8-7 SHOW USE OF 8-11 9. DDL Compiler Commands ANSICOBOL 9-7 C 9-8 Data Definition Language (DDL) Reference Manual—529431-003 iv Contents 9. DDL Compiler Commands (continued) 9. DDL Compiler Commands (continued) C00CALIGN 9-12 CCHECK 9-12 CDEFINEUPPER 9-14 CFIELDALIGN_MATCHED2 9-14 CIFDEF, CIFNDEF, and CENDIF 9-18 CLISTIN 9-20 CLISTOUT 9-21 COBCHECK 9-23 COBLEVEL 9-25 COBOL 9-26 COLUMNS 9-29 COMMENTS 9-29 CPRAGMA 9-32 CTOKENMAP_ASDEFINE 9-32 CUNDEF 9-36 C_DECIMAL 9-37 C_MATCH_HISTORIC_TAL 9-40 DDL 9-42 DEFLIST 9-45 DICT 9-47 DICTN 9-49 DICTR 9-51 DO_PTAL_ON 9-52 EDIT 9-53 ERRORS 9-55 EXPANDC 9-56 FIELDALIGN_SHARED8 9-58 FILLER 9-59 FORCHECK 9-62 FORTRAN 9-63 FORTRANUNDERSCORE 9-66 FUP 9-67 HELP 9-70 LINECOUNT 9-70 LIST 9-71 NCLCONSTANT 9-72 NEWFUP_FILEFORMAT 9-75 NOFILEFORMAT 9-77 Data Definition Language (DDL) Reference Manual—529431-003 v Contents 9. DDL Compiler Commands (continued) 9. DDL Compiler Commands (continued) OLDFUP_FILEFORMAT 9-79 OUT 9-82 OUTPUT_SENSITIVE 9-83 PAGE 9-86 PASCAL (D-Series Systems Only) 9-86 PASCALBOUND (D-Series Systems Only) 9-89 PASCALCHECK (D-Series Systems Only) 9-90 PASCALNAMEDVARIANT (D-Series Only) 9-91 REPORT 9-92 RESET 9-94 SAVE 9-94 SECTION 9-96 SETLOCALENAME 9-97 SETSECTION 9-98 SOURCE 9-99 SPACING 9-101 TACL 9-101 TACLGEN 9-104 TAL 9-105 TALALLOCATE 9-108 TALBOUND 9-109 TALCHECK 9-110 TALUNDERSCORE 9-111 TEDIT 9-112 TIMESTAMP 9-113 VALUES 9-115 WARN 9-116 WARNINGS 9-116 10. Dictionary Maintenance Generating a schema From a Dictionary 10-1 Adding Dictionary Objects 10-2 Deleting Dictionary Objects 10-4 Deleting Unreferenced Objects 10-4 Deleting Referenced Objects 10-5 Modifying Dictionary Objects 10-8 Modifying Unreferenced Objects 10-9 Modifying Referenced Objects 10-10 Data Definition Language (DDL) Reference Manual—529431-003 vi Contents 10. Dictionary Maintenance (continued) 10. Dictionary Maintenance (continued) Making Major Modifications 10-13 Changing Dictionary Security 10-14 Moving a Dictionary 10-14 Moving a Nonaudited Dictionary 10-15 Moving an Audited Dictionary 10-16 Purging a Dictionary 10-18 Increasing Dictionary File Size 10-19 Rebuilding a Dictionary 10-20 Rebuilding a Nonaudited Dictionary 10-20 Rebuilding an Audited Dictionary 10-21 Converting a Dictionary 10-22 A. DDL Messages B. Sample Schemas Sample Database Schema B-1 Host-Language Source Code B-1 Database Schema Listing B-2 Sample SPI Schema B-6 DDL Commands to Create an SPI Schema B-8 Selected ZSPIDDL Statements B-8 ASSNDDL Statements B-10 C.
Load more

Recommended publications
  • Data Definition Language
    1 Structured Query Language SQL, or Structured Query Language is the most popular declarative language used to work with Relational Databases. Originally developed at IBM, it has been subsequently standard- ized by various standards bodies (ANSI, ISO), and extended by various corporations adding their own features (T-SQL, PL/SQL, etc.). There are two primary parts to SQL: The DDL and DML (& DCL). 2 DDL - Data Definition Language DDL is a standard subset of SQL that is used to define tables (database structure), and other metadata related things. The few basic commands include: CREATE DATABASE, CREATE TABLE, DROP TABLE, and ALTER TABLE. There are many other statements, but those are the ones most commonly used. 2.1 CREATE DATABASE Many database servers allow for the presence of many databases1. In order to create a database, a relatively standard command ‘CREATE DATABASE’ is used. The general format of the command is: CREATE DATABASE <database-name> ; The name can be pretty much anything; usually it shouldn’t have spaces (or those spaces have to be properly escaped). Some databases allow hyphens, and/or underscores in the name. The name is usually limited in size (some databases limit the name to 8 characters, others to 32—in other words, it depends on what database you use). 2.2 DROP DATABASE Just like there is a ‘create database’ there is also a ‘drop database’, which simply removes the database. Note that it doesn’t ask you for confirmation, and once you remove a database, it is gone forever2. DROP DATABASE <database-name> ; 2.3 CREATE TABLE Probably the most common DDL statement is ‘CREATE TABLE’.
    [Show full text]
  • Exploring the Visualization of Schemas for Aggregate-Oriented Nosql Databases?
    Exploring the Visualization of Schemas for Aggregate-Oriented NoSQL Databases? Alberto Hernández Chillón, Severino Feliciano Morales, Diego Sevilla Ruiz, and Jesús García Molina Faculty of Computer Science, University of Murcia Campus Espinardo, Murcia, Spain {alberto.hernandez1,severino.feliciano,dsevilla,jmolina}@um.es Abstract. The lack of an explicit data schema (schemaless) is one of the most attractive NoSQL database features for developers. Being schema- less, these databases provide a greater flexibility, as data with different structure can be stored for the same entity type, which in turn eases data evolution. This flexibility, however, should not be obtained at the expense of losing the benefits provided by having schemas: When writ- ing code that deals with NoSQL databases, developers need to keep in mind at any moment some kind of schema. Also, database tools usu- ally require the knowledge of a schema to implement their functionality. Several approaches to infer an implicit schema from NoSQL data have been proposed recently, and some utilities that take advantage of inferred schemas are emerging. In this article we focus on the requisites for the vi- sualization of schemas for aggregate-oriented NoSQL Databases. Schema diagrams have proven useful in designing and understanding databases. Plenty of tools are available to visualize relational schemas, but the vi- sualization of NoSQL schemas (and the variation that they allow) is still in an immature state, and a great R&D effort is required to achieve tools with the desired capabilities. Here, we study the main challenges to be addressed, and propose some visual representations. Moreover, we outline the desired features to be supported by visualization tools.
    [Show full text]
  • SQL: Triggers, Views, Indexes Introduction to Databases Compsci 316 Fall 2014 2 Announcements (Tue., Sep
    SQL: Triggers, Views, Indexes Introduction to Databases CompSci 316 Fall 2014 2 Announcements (Tue., Sep. 23) • Homework #1 sample solution posted on Sakai • Homework #2 due next Thursday • Midterm on the following Thursday • Project mixer this Thursday • See my email about format • Email me your “elevator pitch” by Wednesday midnight • Project Milestone #1 due Thursday, Oct. 16 • See project description on what to accomplish by then 3 Announcements (Tue., Sep. 30) • Homework #2 due date extended to Oct. 7 • Midterm in class next Thursday (Oct. 9) • Open-book, open-notes • Same format as sample midterm (from last year) • Already posted on Sakai • Solution to be posted later this week 4 “Active” data • Constraint enforcement: When an operation violates a constraint, abort the operation or try to “fix” data • Example: enforcing referential integrity constraints • Generalize to arbitrary constraints? • Data monitoring: When something happens to the data, automatically execute some action • Example: When price rises above $20 per share, sell • Example: When enrollment is at the limit and more students try to register, email the instructor 5 Triggers • A trigger is an event-condition-action (ECA ) rule • When event occurs, test condition ; if condition is satisfied, execute action • Example: • Event : some user’s popularity is updated • Condition : the user is a member of “Jessica’s Circle,” and pop drops below 0.5 • Action : kick that user out of Jessica’s Circle http://pt.simpsons.wikia.com/wiki/Arquivo:Jessica_lovejoy.jpg 6 Trigger example
    [Show full text]
  • Oracle Nosql Database EE Data Sheet
    Oracle NoSQL Database 21.1 Enterprise Edition (EE) Oracle NoSQL Database is a multi-model, multi-region, multi-cloud, active-active KEY BUSINESS BENEFITS database, designed to provide a highly-available, scalable, performant, flexible, High throughput and reliable data management solution to meet today’s most demanding Bounded latency workloads. It can be deployed in on-premise data centers and cloud. It is well- Linear scalability suited for high volume and velocity workloads, like Internet of Things, 360- High availability degree customer view, online contextual advertising, fraud detection, mobile Fast and easy deployment application, user personalization, and online gaming. Developers can use a single Smart topology management application interface to quickly build applications that run in on-premise and Online elastic configuration cloud environments. Multi-region data replication Enterprise grade software Applications send network requests against an Oracle NoSQL data store to and support perform database operations. With multi-region tables, data can be globally distributed and automatically replicated in real-time across different regions. Data can be modeled as fixed-schema tables, documents, key-value pairs, and large objects. Different data models interoperate with each other through a single programming interface. Oracle NoSQL Database is a sharded, shared-nothing system which distributes data uniformly across multiple shards in a NoSQL database cluster, based on the hashed value of the primary keys. An Oracle NoSQL Database data store is a collection of storage nodes, each of which hosts one or more replication nodes. Data is automatically populated across these replication nodes by internal replication mechanisms to ensure high availability and rapid failover in the event of a storage node failure.
    [Show full text]
  • KB SQL Database Administrator Guide a Guide for the Database Administrator of KB SQL
    KB_SQL Database Administrator Guide A Guide for the Database Administrator of KB_SQL © 1988-2019 by Knowledge Based Systems, Inc. All rights reserved. Printed in the United States of America. No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from KB Systems, Inc., as governed by United States and international copyright laws. The information contained in this document is subject to change without notice. KB Systems, Inc., does not warrant that this document is free of errors. If you find any problems in the documentation, please report them to us in writing. Knowledge Based Systems, Inc. 43053 Midvale Court Ashburn, Virginia 20147 KB_SQL is a registered trademark of Knowledge Based Systems, Inc. MUMPS is a registered trademark of the Massachusetts General Hospital. All other trademarks or registered trademarks are properties of their respective companies. Table of Contents Preface ................................................. vii Purpose ............................................. vii Audience ............................................ vii Conventions Used in this Manual ...................................................................... viii The Organization of this Manual ......................... ... x Additional Documentation .............................. xii Chapter 1: An Overview of the KB_SQL User Groups and Menus ............................................................................................................
    [Show full text]
  • SUGI 23: an Investigation of the Efficiency of SQL DML Operations Performed on an Oracle DBMS Using SAS/Accessr Software
    Posters An Investigation of the Efficiency of SQL DML Operations Performed on an ORACLE DBMS using SAS/ACCESS Software Annie Guo, Ischemia Research and Education Foundation, San Francisco, California Abstract Table 1.1: Before Modification Of Final Records Id Entry MedCode Period1 Period2 Indication AG1001 Entry1 AN312 Postop Day1 Routine AG1001 Entry2 AN312 Postop Day1 Routine In an international epidemiological study of 2000 cardiac AG1001 Final AN312 Postop Day1 Non-routine ← To be updated surgery patients, the data of 7000 variables are entered AG1001 Final HC527 Intraop PostCPB Maintenance ← To be deleted AG1002 Entry1 PV946 Intraop PreCPB Non-routine ← To be inserted through a Visual Basic data entry system and stored in 57 AG1002 Entry2 PV946 Intraop PreCPB Non-routine as ‘Final’ large ORACLE tables. A SAS application is developed to Table 1.2: After Modification Of Final Records automatically convert the ORACLE tables to SAS data sets, Id Entry MedCode Period1 Period2 Indication AG1001 Entry1 AN312 Postop Day1 Routine perform a series of intensive data processing, and based AG1001 Entry2 AN312 Postop Day1 Routine AG1001 Final AN312 Postop Day1 Routine ← Updated upon the result of the data processing, dynamically pass AG1002 Entry1 PV946 Intraop PreCPB Non-routine AG1002 Entry2 PV946 Intraop PreCPB Non-routine ORACLE SQL Data Manipulation Language (DML) AG1002 Final PV946 Intraop PreCPB Non-routine ← Inserted commands such as UPDATE, DELETE and INSERT to ORACLE database and modify the data in the 57 tables. A Visual Basic module making use of ORACLE Views, Functions and PL/SQL Procedures has been developed to The modification of ORACLE data using SAS software can access the ORACLE data through ODBC driver, compare be resource-intensive, especially in dealing with large tables the 7000 variables between the 2 entries, and modify the and involving sorting in ORACLE data.
    [Show full text]
  • IEEE Paper Template in A4 (V1)
    International Journal of Electrical Electronics & Computer Science Engineering Special Issue - NCSCT-2018 | E-ISSN : 2348-2273 | P-ISSN : 2454-1222 March, 2018 | Available Online at www.ijeecse.com Structural and Non-Structural Query Language Vinayak Sharma1, Saurav Kumar Jha2, Shaurya Ranjan3 CSE Department, Poornima Institute of Engineering and Technology, Jaipur, Rajasthan, India [email protected], [email protected], [email protected] Abstract: The Database system is rapidly increasing and it The most important categories are play an important role in all commercial-scientific software. In the current scenario every field work is related to DDL (Data Definition Language) computer they store their data in the database. Using DML (Data Manipulation Language) database helps to maintain the large records. This paper aims to summarize the different database and their usage in DQL (Data Query Language) IT field. In company database is more appropriate or more 1. Data Definition Language: Data Definition suitable to store the data. Language, DDL, is the subset of SQL that are used by a Keywords: DBS, Database Management Systems-DBMS, database user to create and built the database objects, Database-DB, Programming Language, Object-Oriented examples are deletion or the creation of a table. Some of System. the most Properties of DDL commands discussed I. INTRODUCTION below: CREATE TABLE The database system is used to develop the commercial- scientific application with database. The application DROP INDEX requires set of element for collection transmission, ALTER INDEX storage and processing of data with computer. Database CREATE VIEW system allow the database develop application. This ALTER TABLE paper deal with the features of Nosql and need of Nosql in the market.
    [Show full text]
  • 3 Data Definition Language (DDL)
    Database Foundations 6-3 Data Definition Language (DDL) Copyright © 2015, Oracle and/or its affiliates. All rights reserved. Roadmap You are here Data Transaction Introduction to Structured Data Definition Manipulation Control Oracle Query Language Language Language (TCL) Application Language (DDL) (DML) Express (SQL) Restricting Sorting Data Joining Tables Retrieving Data Using Using ORDER Using JOIN Data Using WHERE BY SELECT DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 3 Data Definition Language (DDL) Objectives This lesson covers the following objectives: • Identify the steps needed to create database tables • Describe the purpose of the data definition language (DDL) • List the DDL operations needed to build and maintain a database's tables DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 4 Data Definition Language (DDL) Database Objects Object Description Table Is the basic unit of storage; consists of rows View Logically represents subsets of data from one or more tables Sequence Generates numeric values Index Improves the performance of some queries Synonym Gives an alternative name to an object DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 5 Data Definition Language (DDL) Naming Rules for Tables and Columns Table names and column names must: • Begin with a letter • Be 1–30 characters long • Contain only A–Z, a–z, 0–9, _, $, and # • Not duplicate the name of another object owned by the same user • Not be an Oracle server–reserved word DFo 6-3 Copyright © 2015, Oracle and/or its affiliates. All rights reserved. 6 Data Definition Language (DDL) CREATE TABLE Statement • To issue a CREATE TABLE statement, you must have: – The CREATE TABLE privilege – A storage area CREATE TABLE [schema.]table (column datatype [DEFAULT expr][, ...]); • Specify in the statement: – Table name – Column name, column data type, column size – Integrity constraints (optional) – Default values (optional) DFo 6-3 Copyright © 2015, Oracle and/or its affiliates.
    [Show full text]
  • Introduction to Database
    ST. LAWRENCE HIGH SCHOOL A Jesuit Christian Minority Institution STUDY MATERIAL - 12 Subject: COMPUTER SCIENCE Class - 12 Chapter: DBMS Date: 01/08/2020 INTRODUCTION TO DATABASE What is Database? The database is a collection of inter-related data which is used to retrieve, insert and delete the data efficiently. It is also used to organize the data in the form of a table, schema, views, and reports, etc. For example: The college Database organizes the data about the admin, staff, students and faculty etc. Using the database, you can easily retrieve, insert, and delete the information. Database Management System Database management system is a software which is used to manage the database. For example: MySQL, Oracle, etc. are a very popular commercial database which is used in different applications. DBMS provides an interface to perform various operations like database creation, storing data in it, updating data, creating a table in the database and a lot more. It provides protection and security to the database. In the case of multiple users, it also maintains data consistency. DBMS allows users the following tasks: Data Definition: It is used for creation, modification, and removal of definition that defines the organization of data in the database. Data Updation: It is used for the insertion, modification, and deletion of the actual data in the database. Data Retrieval: It is used to retrieve the data from the database which can be used by applications for various purposes. User Administration: It is used for registering and monitoring users, maintain data integrity, enforcing data security, dealing with concurrency control, monitoring performance and recovering information corrupted by unexpected failure.
    [Show full text]
  • Today SQL Views CREATE VIEW Command
    Today IT420: Database Management and SQL Views Organization SQL Views (Chapter 7) 1 Kroenke, Database Processing 2 SQL Views CREATE VIEW Command SQL view is a virtual table that is constructed from other CREATE VIEW command: tables or views CREATE VIEW view_name It has no data of its own, but obtains data from tables or AS other views select_statement It only has a definition Use the view: SELECT statements are used to define views In SELECT statements A view definition may not include an ORDER BY clause Sometimes in INSERT statements Views can be used as regular tables in SELECT Sometimes in UPDATE statements statements Sometimes in DELETE statements Kroenke, Database Processing 3 Kroenke, Database Processing 4 1 CREATE VIEW Command Uses for SQL Views CREATE VIEW Security: hide columns and rows command: CREATE VIEW CustomerNameView Display results of computations AS Hide complicated SQL syntax SELECT CustName AS CustomerName Provide a level of isolation between actual FROM CUSTOMER; data and the user’s view of data To use the view: three-tier architecture SELECT * Assign different processing permissions to FROM CustomerNameView ORDER BY CustomerName; different views on same table Kroenke, Database Processing 5 Kroenke, Database Processing 6 Security: hide columns and rows Display results of computations MIDS database, Midshipmen table Faculty (EmpID , LName, FName, Department, AreaCode, LocalPhone) View for faculty – all mids with IT major Create a view to display 2 columns: View for students – all mids, no
    [Show full text]
  • Database Views
    DATABASE VIEWS CHAPTER 5 (6/E) CHAPTER 8 (5/E) 1 LECTURE OUTLINE . Database views provide convenient usage • Virtual view realized when query uses that view . Materialized views allow efficient re-use • Must be recalculated or updated when base tables change 2 VIEWS FOR CUSTOMIZATION . Consider database(s) describing university’s activities • Academic institution • Students, professors, classes • Grades, transcripts • Admissions, convocations • Alumni • Corporate institution • Finances, human resources • Board of Governors • Capital assets • Charitable institution • Donors, fundraising activities • Research institution • Granting agencies, industrial/non-profits/academic partners • Grants and contracts, intellectual property, licensing . Each user group provided appropriate “subset” of the data • e.g., some financial/scheduling info relevant to most groups; other info confidential • Underlying data shared, not silo’d. Updates must be seen by all affected users. 3 VIEWS (VIRTUAL TABLES) . Consider again the query SELECT title, year, genre FROM Film WHERE director = 'Steven Spielberg' AND year > 1990; • Returns all matching films currently in the database • If re-run after updates, will give revised table of matches . A view is an unexecuted query that can be run on demand. • Single table derived from other table(s) • A virtual table 4 USING VIEWS IN SQL . CREATE VIEW command • View name and a query to specify the contents of the view CREATE VIEW Big_Earners AS SELECT E.Ssn AS Ssn, E.Lname AS Name, E.Salary AS Salary, M.Lname AS Manager FROM EMPLOYEE E, EMPLOYEE M WHERE E.Super_ssn = M.Ssn and E.Salary > M.Salary; . Queries can use view as if it were a base table. SELECT * FROM Big_Earners WHERE Salary < 100000; .
    [Show full text]
  • Short Type Questions and Answers on DBMS
    BIJU PATNAIK UNIVERSITY OF TECHNOLOGY, ODISHA Short Type Questions and Answers on DBMS Prepared by, Dr. Subhendu Kumar Rath, BPUT, Odisha. DABASE MANAGEMENT SYSTEM SHORT QUESTIONS AND ANSWERS Prepared by Dr.Subhendu Kumar Rath, Dy. Registrar, BPUT. 1. What is database? A database is a logically coherent collection of data with some inherent meaning, representing some aspect of real world and which is designed, built and populated with data for a specific purpose. 2. What is DBMS? It is a collection of programs that enables user to create and maintain a database. In other words it is general-purpose software that provides the users with the processes of defining, constructing and manipulating the database for various applications. 3. What is a Database system? The database and DBMS software together is called as Database system. 4. What are the advantages of DBMS? 1. Redundancy is controlled. 2. Unauthorised access is restricted. 3. Providing multiple user interfaces. 4. Enforcing integrity constraints. 5. Providing backup and recovery. 5. What are the disadvantage in File Processing System? 1. Data redundancy and inconsistency. 2. Difficult in accessing data. 3. Data isolation. 4. Data integrity. 5. Concurrent access is not possible. 6. Security Problems. 6. Describe the three levels of data abstraction? The are three levels of abstraction: 1. Physical level: The lowest level of abstraction describes how data are stored. 2. Logical level: The next higher level of abstraction, describes what data are stored in database and what relationship among those data. 3. View level: The highest level of abstraction describes only part of entire database.
    [Show full text]