DOCSLIB.ORG

DATA BASE MANAGEMENT SYSTEMS Unit

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
DATA BASE MANAGEMENT SYSTEMS Unit BCA204T: DATA BASE MANAGEMENT SYSTEMS Page 1 of 29 BCA204T: DATA BASE MANAGEMENT SYSTEMS Unit - I Introduction: Database and Database Users, Characteristics of the Database Approach, Different people behind DBMS, Implications of Database Approach, Advantages of using DBMS, When not to use a DBMS. Database System Concepts and architecture: Data Models, Schemas, and Instances. DBMS Architecture and Data Independence., Database languages and interfaces. The database system Environment, Classification of DBMS. ____________________________________ www.gkmvkalyan.blogspot.in BCA204T: DATA BASE MANAGEMENT SYSTEMS Page 2 of 29 Unit-I Introduction Introduction: Database is a collection of related data. Database management system is software designed to assist the maintenance and utilization of large scale collection of data. DBMS came into existence in 1960 by Charles. Integrated data store which is also called as the first general purpose DBMS. Again in 1960 IBM brought IMS-Information management system. In 1970 Edgor Codd at IBM came with new database called RDBMS. In 1980 then came SQL Architecture- Structure Query Language. In 1980 to 1990 there were advances in DBMS e.g. DB2, ORACLE. Data: Data is raw fact or figures or entity. Information: The processed data is called information. Database: A database is a collection of related data. For example, a university database might contain information about the following: . Entities such as students, faculty and courses. Relationships between entities, such as students' enrollment in courses, faculty teaching courses. Database Management System: A Database Management System (DBMS) is a collection of program that enables user to create, maintain and manipulate a database. The DBMS is hence a general purpose software system that facilitates the process of defining, constructing and manipulating database for various applications. ____________________________________ www.gkmvkalyan.blogspot.in BCA204T: DATA BASE MANAGEMENT SYSTEMS Page 3 of 29 Characteristics of DBMS • To incorporate the requirements of the organization, system should be designed for easy maintenance. • Information systems should allow interactive access to data to obtain new information without writing fresh programs. • System should be designed to co-relate different data to meet new requirements. • An independent central repository, which gives information and meaning of available data is required. • Integrated database will help in understanding the inter-relationships between data stored in different applications. • The stored data should be made available for access by different users simultaneously. • Automatic recovery feature has to be provided to overcome the problems with processing system failure. ____________________________________ www.gkmvkalyan.blogspot.in BCA204T: DATA BASE MANAGEMENT SYSTEMS Page 4 of 29 Different people behind DBMS These apply to "large" databases, not "personal" databases that are defined, constructed, and used by a single person via, say, Microsoft Access. There are two categories of people behind DBMS a) Those who actually use and control the database content, and those who design, develop and maintain database applications (called ―Actors on the Scene) b) Those who design and develop the DBMS software and related tools, and the computer systems operators (called ―Workers Behind the Scene). a) Actors on the Scene 1. Database Administrator (DBA): DBA is a person who is responsible for authorizing access to the database, coordinating and monitoring its use, and acquiring software and hardware resources as needed. 2. Database Designers: They are responsible for identifying the data to be stored and for choosing an appropriate way to organize it. They also define views for different categories of users. The final design must be able to support the requirements of all the user sub-groups. 3. End Users: These are persons who access the database for querying, updating, and report generation. They are main reason for database's existence! o Casual end users: use database occasionally, needing different information each time; use query language to specify their requests; typically middle- or high- level managers. o Naive/Parametric end users: Typically the biggest group of users; frequently query/update the database using standard canned transactions that have been carefully programmed and tested in advance. Examples: ____________________________________ www.gkmvkalyan.blogspot.in BCA204T: DATA BASE MANAGEMENT SYSTEMS Page 5 of 29 . bank tellers check account balances, post withdrawals/deposits . reservation clerks for airlines, hotels, etc., check availability of seats/rooms and make reservations. o Sophisticated end users: engineers, scientists, business analysts who implement their own applications to meet their complex needs. o Stand-alone users: Use "personal" databases, possibly employing a special- purpose (e.g., financial) software package. Mostly maintain personal databases using ready-to-use packaged applications. o An example is a tax program user that creates its own internal database. o Another example is maintaining an address book 4. System Analysts, Application Programmers, Software Engineers: o System Analysts: determine needs of end users, especially naive and parametric users, and develop specifications for canned transactions that meet these needs. o Application Programmers: Implement, test, document, and maintain programs that satisfy the specifications mentioned above. b) Workers Behind the Scene 1)DBMS system designers/implementors: provide the DBMS software that is at the foundation of all this! 2) Tool developers: design and implement software tools facilitating database system design, performance monitoring, creation of graphical user interfaces, prototyping, etc. 3) Operators and maintenance personnel: responsible for the day-to-day operation of the system. ____________________________________ www.gkmvkalyan.blogspot.in BCA204T: DATA BASE MANAGEMENT SYSTEMS Page 6 of 29 Advantages of a DBMS Using a DBMS to manage data has many advantages: Data independence: Application programs should be as independent as possible from details of data representation and storage. The DBMS can provide an abstract view of the data to insulate application code from such details. Efficient data access: A DBMS utilizes a variety of sophisticated techniques to store and retrieve data efficiently. This feature is especially important if the data is stored on external storage devices. Data integrity and security: If data is always accessed through the DBMS, the DBMS can enforce integrity constraints on the data. For example, before inserting salary information for an employee, the DBMS can check that the department budget is not exceeded. Also, the DBMS can enforce access controls that govern what data is visible to different classes of users. Data administration: When several users share the data, centralizing the administration of data can offer significant improvements. Experienced professionals who understand the nature of the data being managed, and how different groups of users use it, can be responsible for organizing the data representation to minimize redundancy and for fine-tuning the storage of the data to make retrieval efficient. Concurrent access and crash recovery: A DBMS schedules concurrent accesses to the data in such a manner that users can think of the data as being accessed by only one user at a time. Further, the DBMS protects users from the effects of system failures. Reduced application development time: Clearly, the DBMS supports many important functions that are common to many applications accessing data stored in the DBMS. This, in conjunction with the high-level interface to the data, facilitates quick development of applications. Such applications are also likely to be more robust than applications developed from scratch because many important tasks are handled by the DBMS instead of being implemented by the application. ____________________________________ www.gkmvkalyan.blogspot.in BCA204T: DATA BASE MANAGEMENT SYSTEMS Page 7 of 29 Functions of DBMS • Data Definition: The DBMS provides functions to define the structure of the data in the application. These include defining and modifying the record structure, the type and size of fields and the various constraints to be satisfied by the data in each field. • Data Manipulation: Once the data structure is defined, data needs to be inserted, modified or deleted. These functions which perform these operations are part of DBMS. These functions can handle plashud and unplashud data manipulation needs. Plashud queries are those which form part of the application. Unplashud queries are ad-hoc queries which performed on a need basis. • Data Security & Integrity: The DBMS contains modules which handle the security and integrity of data in the application. • Data Recovery and Concurrency: Recovery of the data after system failure and concurrent access of records by multiple users is also handled by DBMS. • Data Dictionary Maintenance: Maintaining the data dictionary which contains the data definition of the application is also one of the functions of DBMS. • Performance: Optimizing the performance of the queries is one of the important functions of DBMS. When not to use a DBMS a) Main inhibitors (costs) of using a DBMS: i) High initial investment and possible need for additional hardware. ii) Overhead for providing generality, security, concurrency control, recovery, and integrity functions. b) When a DBMS may be unnecessary:
Load more

Recommended publications
  • PL/SQL User's Guide and Reference 10G Release 1 (10.1) Part No
    PL/SQL User's Guide and Reference 10g Release 1 (10.1) Part No. B10807-01 December 2003 PL/SQL User's Guide and Reference, 10g Release 1 (10.1) Part No. B10807-01 Copyright © 1996, 2003 Oracle. All rights reserved. Primary Author: John Russell Contributors: Shashaanka Agrawal, Cailein Barclay, Dmitri Bronnikov, Sharon Castledine, Thomas Chang, Ravindra Dani, Chandrasekharan Iyer, Susan Kotsovolos, Neil Le, Warren Li, Bryn Llewellyn, Chris Racicot, Murali Vemulapati, Guhan Viswanathan, Minghui Yang The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
    [Show full text]
  • Quick Reference to SQL and SQL*Plus
    APPENDIX A ■ ■ ■ Quick Reference to SQL and SQL*Plus This appendix offers quick references for SQL*Plus and the SQL language. It is far from a com- plete reference, but it should still prove useful. The Oracle documentation contains (besides the comprehensive and complete references) an SQL Quick Reference and a SQL*Plus Quick Reference, but this appendix is much more concise than those two Oracle quick references. You may abbreviate most SQL*Plus commands and their components, as long as you don’t introduce ambiguity. This appendix does not show all SQL*Plus command abbreviation possibilities explicitly, in order to enhance its readability. For example, where this appendix lists the COMPUTE command, it should show it as COMP[UTE], because you can abbreviate the SQL*Plus COMPUTE command to COMP. Abbreviation is available only for SQL*Plus commands; you must always enter SQL commands completely. Refer to SQL*Plus User’s Guide and Reference for all of the abbreviations for SQL*Plus commands and their components. ■Tip When writing SQL*Plus scripts, use the full SQL*Plus commands and the full command component names instead of their abbreviations. This will enhance the readability of your scripts. When you are using SQL*Plus interactively, you may want to use the abbreviations. There are some differences between SQL*Plus and iSQL*Plus; however, this appendix does not list those differences. Refer to SQL*Plus User’s Guide and Reference for more details. The Oracle documentation also explicitly shows all abbreviations for SQL*Plus commands and
    [Show full text]
  • PL/SQL User's Guide and Reference 10G Release 2 (10.2) B14261-01
    Oracle® Database PL/SQL User's Guide and Reference 10g Release 2 (10.2) B14261-01 June 2005 Oracle Database PL/SQL User’s Guide and Reference 10g Release 2 (10.2) B14261-01 Copyright © 1996, 2005, Oracle. All rights reserved. Contributors: Shashaanka Agrawal, Cailein Barclay, Eric Belden, Dmitri Bronnikov, Sharon Castledine, Thomas Chang, Ravindra Dani, Chandrasekharan Iyer, Susan Kotsovolos, Neil Le, Warren Li, Bryn Llewellyn, Valarie Moore, Chris Racicot, Murali Vemulapati, John Russell, Guhan Viswanathan, Minghui Yang The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
    [Show full text]
  • SQL Engine Reference
    Pervasive.SQL 2000i SQL Engine Reference Reference for Using SQL with Pervasive.SQL 2000 Service Pack 3 Pervasive Software, Inc. 12365 Riata Trace Parkway Building II Austin, TX 78727 USA Telephone: +1 512 231 6000 or 800 287 4383 Fax: +1 512 231 6010 E-Mail: [email protected] Web: http://www.pervasive.com disclaimer PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN “AS IS” BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT. PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, INCLUDING, FOR EXAMPLE, WITH RESPECT TO MERCHANTABILITY, TITLE, OR FITNESS FOR ANY PARTICULAR PURPOSE OR ARISING FROM COURSE OF DEALING OR USAGE OF TRADE, AMONG OTHERS. trademarks Btrieve, Tango, Client/Server in a Box, and the Pervasive Software logo are registered trademarks of Pervasive Software Inc. Built on Pervasive, Built on Pervasive Software, Extranet in a Box, Pervasive.SQL, Jtrieve, Plug n’ Play Databases, SmartScout, Solution Network, Ultra-light Z-DBA, Z-DBA, ZDBA, UltraLight, MicroKernel Database Engine, and MicroKernel Database Architecture are trademarks of Pervasive Software Inc. Microsoft, MS-DOS, Windows, Windows NT, Win32, Win32s, and Visual Basic are registered trademarks of Microsoft Corporation. Windows 95 is a trademark of Microsoft Corporation. NetWare and Novell are registered trademarks of Novell, Inc. NetWare Loadable Module, NLM, Novell DOS, Transaction Tracking System, and TTS are trademarks of Novell, Inc.
    [Show full text]
  • Programmer's Guide to the Oracle Precompilers Release 10.2
    Oracle® Database Programmer’s Guide to the Oracle Precompilers 10g Release 2 (10.2) B14354-01 June 2005 Oracle Database Programmer’s Guide to the Oracle Precompilers, 10g Release 2 (10.2) B14354-01 Copyright © 2001, 2005, Oracle. All rights reserved. Primary Author: Tom Portfolio Contributing Author: Jack Godwin Contributor: Stephen Arnold, Sanford Dreskin, Pierre Dufour, Steve Faris, Radhakrishna Hari, Nancy Ikeda, Ken Jacobs, Maura Joglekar, Phil Locke, Valarie Moore, Lee Osborne, Jacqui Pons, Tim Smith, Gael Turk, Scott Urman, Peter Vasterd The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
    [Show full text]
  • Memo to Users Version 7.4
    IBM i Memo to Users Version 7.4 Memo to Users IBM Note Before using this information and the product it supports, read the information in “Notices” on page 33. This edition applies to version IBM i 7.4 (product number 5770-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright International Business Machines Corporation 1998, 2019. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Chapter 1. PDF file for Memorandum to Users.........................................................1 Chapter 2. About IBM i Memo to Users....................................................................3 Who should read this memorandum........................................................................................................... 3 Additional incompatibility information........................................................................................................3 What's new...................................................................................................................................................3 Installing IBM i 7.4 over IBM i 7.2...............................................................................................................4
    [Show full text]
  • Mn/DOT Physical Data Modeling and Implementation Standards
    Mn/DOT Physical Data Modeling And Implementation Standards Mn/DOT Database Administrators Team Version 2.1 Date: August 2011 Mn/DOT Physical Data Modeling and Implementation Standards Version 2.0 Page 1 of 116 Version History Modified By | Date Version Section(s) Comment Approved By Initial Draft taken from Mike’s documentation, useful content 2/11/2010 1.0 found on the Web, and Team additions. Additions made from comments 2/22/2010 1.1 from the 2/11/2009 DBA Team Meeting. Additions made from comments 3/4/2010 1.2 from the 2/22/2010 DBA Team Meeting. Additions made from comments 3/12/2010 1.3 from the 3/11/2010 DBA Team Meeting. Additions made from comments 3/26/2010 1.4 from the 3/25/2010 DBA Team Meeting. 6//2010 1.5 Final Draft Review 6/22/2010 2.0 1st Published Version 8/8/2011 2.1 PL Added Abbreviations/Acronyms 9/23/2011 2.2 PL Added Dimensional Physical Mn/DOT Physical Data Modeling and Implementation Standards Version 2.0 Page 2 of 116 Table of Contents PHYSICAL DATA MODELING STANDARD ................................................................................................................ 6 PURPOSE ........................................................................................................................................................... 6 SCOPE ................................................................................................................................................................ 6 STANDARD .......................................................................................................................................................
    [Show full text]
  • CA Ideal for CA Datacom Programming Guide
    Programming Guide Version 14.02 This Documentation, which includes embedded help systems and electronically distributed materials (hereinafter referred to as the “Documentation”), is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT.
    [Show full text]
  • PROC SQL: Beyond the Basics Using SAS PROC SQL Beyond the Basics Using SAS® Second Edition ® Lafler
    PROC SQL: Beyond the Basics Using SAS Using Basics the Beyond SQL: PROC PROC SQL Beyond the Basics Using SAS® Second Edition ® Lafler Kirk Paul Lafler From PROC SQL, Second Edition. Full book available for purchase here. Contents About This Book .......................................................................................xv About The Author .................................................................................... xix Acknowledgments ................................................................................... xxi Chapter 1: Designing Database Tables ...................................................... 1 Introduction .................................................................................................................................... 2 Database Design ............................................................................................................................ 2 Conceptual View ...................................................................................................................... 2 Table Definitions ...................................................................................................................... 3 Redundant Information ........................................................................................................... 3 Normalization ........................................................................................................................... 4 Normalization Strategies .......................................................................................................
    [Show full text]
  • PL/SQL User's Guide and Reference
    PL/SQL User’s Guide and Reference Release 2 (9.2) March 2002 Part No. A96624-01 PL/SQL User’s Guide and Reference, Release 2 (9.2) Part No. A96624-01 Copyright © 1996, 2002 Oracle Corporation. All rights reserved. Primary Author: John Russell Contributing Author: Tom Portfolio Contributors: Shashaanka Agrawal, Cailein Barclay, Dmitri Bronnikov, Sharon Castledine, Thomas Chang, Ravindra Dani, Chandrasekharan Iyer, Susan Kotsovolos, Neil Le, Warren Li, Chris Racicot, Murali Vemulapati, Guhan Viswanathan, Minghui Yang The Programs (which include both the software and documentation) contain proprietary information of Oracle Corporation; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent and other intellectual and industrial property laws. Reverse engineering, disassembly or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle Corporation. If the Programs are delivered to the U.S. Government or anyone licensing or using the programs on behalf of the U.S. Government, the following notice is applicable: Restricted Rights Notice Programs delivered subject to the DOD FAR Supplement are "commercial computer software" and use, duplication, and disclosure of the Programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement.
    [Show full text]
  • Tactics for Pushing SQL to the Relational Databases
    Tactics for Pushing SQL to the Relational Technical Paper Databases December 2008 Tactics for Pushing SQL to Relational Databases Table of Contents Introduction ....................................................................................................................1 Audience for this Paper .............................................................................................1 Purpose of the Paper.................................................................................................1 Scope of This Paper ..................................................................................................1 Overview....................................................................................................................1 Background for This Paper........................................................................................2 Important Concepts ...................................................................................................3 SAS/ACCESS® Software ....................................................................................3 SAS/ACCESS® Interface to ODBC.....................................................................3 SAS/ ACCESS Interface to OLE DB...................................................................3 Databases, Relational Databases, and Relational Database Management Systems (RDBMS) ............................................................................................................................4 Using SAS to Analyze Relational Database Information
    [Show full text]
  • Derby Reference Manual Version 10.15
    Derby Reference Manual Version 10.15 Derby Document build: February 4, 2020, 5:03:53 PM (PST) Version 10.15 Derby Reference Manual Contents Copyright..............................................................................................................................11 License................................................................................................................................. 12 About this guide..................................................................................................................16 Purpose of this document...................................................................................... 16 Audience................................................................................................................... 16 How this guide is organized...................................................................................16 SQL syntax used in this manual............................................................................17 SQL language reference.....................................................................................................18 Capitalization and special characters....................................................................18 SQL identifiers ........................................................................................................ 18 Rules for SQL identifiers..................................................................................... 19 SQLIdentifier.......................................................................................................
    [Show full text]