Unit 2 File Concepts and File Structure

Total Page:16

File Type:pdf, Size:1020Kb

Unit 2 File Concepts and File Structure UNIT 2 FILE CONCEPTS AND FILE STRUCTURE Structure 2.0 Objectives 2.1 Introduction 2.2 File Organisation 2.2.1 Sequential File Organisation 2.2.2 Indexed Sequential File 2.3 Random Access File Organisation 2.4 Multi-key File Organisation 2.4.1 Multilist File Organisation 2.4.2 Inverted File Organisation 2.5 Summary 2.6 Answers to Self Check Exercises 2.7 Keywords 2.8 References and Further Reading 2.0 OBJECTIVES In the preceding Unit of this block you have learnt about the Database Concepts and various types of databases and database models. You have seen that the files are main ingredient of databases. In this Unit you will learn the concepts of files in the computer environment and also how such files are organised. After the completion of this unit, you will be able to: define what is file organisation and discuss its different types; understand various file organisation techniques; and discuss various types of indexes used in file organisation. 2.1 INTRODUCTION Generally speaking, a file consists of a collection of records. A key element in file management is concerned with the ways in which the records themselves are organised inside the file, since this affects system performances heavily as far as record finding and access are concerned. Here, by “organisation”, we refer to the logical arrangement of the records in a file (their ordering or, more generally, the presence of ``closeness’’ relations between them based on their content), and not to the physical layout of the file as stored on a storage media. However, access method of records in a file is dependent upon the physical medium on which the files, records are stored. Magnetic tape is sequential by its very nature. To read a record you must start at the beginning of the tape and sequentially read each record one after another (sequentially) until you get to 28 the one you want just like when you listen a song recorded in a audio tape. With disks, of course, random access of records is possible. It is the same as the difference between audio cassette and audio compact disc. In audio tape, File Concepts and File you have to start at the beginning and run the tape forward until you get to the Structure song you want to hear. With compact disc you can play the songs in random order or go directly to the track you want to hear. In this unit, we will be discussing about the ways data are represented for files on external storage devices so that required functions (e.g., retrieval, update) may be carried out efficiently. A particular organisation method most suitable for any application will depend upon such factors, as the kind of external storage available, types of queries allowed, number of keys, mode of retrieval and mode of update. 2.2 FILE ORGANISATION The technique used to represent and store the records in a file is known as file organisation. Thus a file is a named collection of related data or facts. Fields are the columns containing one type of information. File is a group of all the records. Therefore, a file contains Records and Records contain fields; Fields contain data items; Data items contain characters (alphabets, digits, special characters, etc.). Each character occupies one byte for its storage. Characters Fields Records File Fig. 2.1: Components of a File In the context of a traditional library the author catalogue is a file. Each individual author catalogue card is a record. Each area in a card such as author, title etc. is field. Thus, file may consist of one or more records, a record may consist of one or more fields and so on. A database is a collection of files that together implement a logical data model. Therefore, file organisation refers to the method used in organising data for storage, retrieval and processing. The two types of files in a physical database structure are data files and index files. Data files store the facts that comprise the database. Index files (or directories) support access to the data files but usually do not themselves store facts other than key values. A database’s logical structure helps in determining which facts should be accessed and how these facts relate to one another. Consider a simple bibliographical database. It may consist of a file of records containing bibliographical details about books. Each record about a book may consist of several fields (Author, Title, Imprint, etc.). For fast access to the 29 Database Concepts records we may create another file, an index file or inverted file – each record in which may hold the index term (Name of author, Subject descriptor, etc.) and an index number. It is similar to back of the book index. The organisation of file determines the sequence of a file’s record, which is the physical ordering of records in storage. It also determines the set of operations necessary to find particular records. Record Access Method The method of organising the record in a file is referred to as its structure or organisation. The method by which we search the file in order to retrieve data is called the access method. Since the type of structure determines the possible means of access and vice ersa, these two elements, structure/organisation and access method, are intertwined. Table 1: Record access for different file organisations File Organisation Sup Sequential Seq Direct Seq Indexed Seq For a particular file the most appropriate organisation is determined on the basis of the operational characteristics of the storage medium used and the nature of the operations to be performed on the data. The most important characteristic of a storage device to be considered is whether it allows direct access to particular record occurrences or allows only sequential access to record occurrences. Magnetic disks are examples of direct access storage devices (abbreviated DASD’s). Magnetic tapes are examples of sequential storage devices. The four basic file organisation techniques that we will discuss here are the following: 1) Sequential 2) Indexed sequential 3) Random Access 4) Multi-key 2.2.1 Sequential File Organisation Sequential file organisation is the simplest file organisation technique. In a sequentially organised file, records are written in a sequence in one long list. The records in the file are arranged, in the same sequence in which they were originally entered/written into the file. That is, the records of the file are stored one after another e.g. record with sequence number 11 located just after the 10th record. 30 Beginning of Record 1 File Concepts and File ○○○○○○○○○○○ Structure file Record 2 ○○ ○○ Record n-1 Record N End of file Fig. 2.2: Structure of Sequential File The file is read from the beginning in the sequence in which the records are arranged. Thus, in a simple sequential file, the one way to retrieve the data is to start at the beginning of the file and read one record after the other, in sequence, until you reach the record you are searching for. The search is sequential, record by record. This can be time consuming especially for large files. In searching large databases, such sequential method takes relatively more time to identify and retrieve particular records, in comparison with other files. A sequential file could be stored on a sequential storage device such as a magnetic tape. Sequential files are, however, suitable for storing only archive, backup, and transport copies databases. Updating a sequential file usually requires the creation of a new file. To maintain file sequence, records are copied to the point where amendment is required. The changes are then made and copied into the new file. Following this, the remaining records in the original file are copied to the new file. The basic advantage offered by a sequential file is the ease of access to the next record, the simplicity of organisation and the absence of auxiliary data structures. However, replies to simple queries are time consuming for large files. In sequential file in addition to the problem of simple access, there are problems in the insertion and deletion of records. The drawback of a sequential file is that once a sequential file is created, records can be added only at the end of the file. It is not possible to insert records in the middle of the file without rewriting the file. And it is also not possible to modify an existing record without rewriting the file. To delete a record you should locate it first. 2.2.2 Indexed-Sequential File Indexed sequential file is designed to overcome the limitations of the sequential file. In indexed sequential file, a file is sequenced on a particular field, and an index for that file is built, based on that very field. Thus in indexed sequential file a type of indexing technique is added. The index provides a mechanism for faster search. Through indexing, a set of objects is associated to a set of orderable quantities. The indexed sequential file organisation allows both sequential and random processing. A sequential (or sorted on primary keys) file that is indexed is called an indexed sequential file. The index provides for random access to records, while the sequential nature of the file provides easy access to the subsequent records as well as sequential processing. An additional feature of this file system is the overflow area. This feature provides additional space for record addition without necessitating the creation of a new file. Before starting discussion on indexed 31 Database Concepts sequential file structure, let us, discuss the types of indexes which may be possible.
Recommended publications
  • CA XCOM Data Transport for Z/OS User Guide
    CA XCOM™ Data Transport® for z/OS User Guide Version 12.0.00 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 is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. 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. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
    [Show full text]
  • ACUCOBOL-GT | Open Systems COBOL Compiler and Runtime System
    ® ACUCOBOL-GT | Open Systems COBOL Compiler and Runtime System EXECUTIVE OVERVIEW ACUCOBOL-GT is an advanced COBOL development system for extending and modernizing business-critical COBOL applications. It is an extremely portable COBOL, supporting single- source, compile-once deployment on hundreds of platforms including most UNIX®, Linux®, Windows®, VMS, and MPE/iX systems. ACUCOBOL-GT includes extensive facilities for interoperating with C, Java, .NET and XML. It supports connectivity to leading relational databases and ISAM data sources through both open and patented technologies. The core component of ® Imagine. COBOL interoperating with Java™ Acucorp’s family of extend technologies, ACUCOBOL-GT supports thin client and multi-tier technology... running a .NET™ assembly… client/server architectures, as well as COBOL Web processing XML data…or providing a Web services and platform-independent graphical user service. Imagine running COBOL from a mobile, interfaces. Flexible and scalable, ACUCOBOL-GT handheld device. What would this kind of works anywhere in the enterprise, from back office to point-of-sale. functionality mean to your business? For some, it might give a competitive edge, adding value to ACUCOBOL-GT is a multi-component COBOL mission-critical applications. To others it might development system that includes a compiler, the mean breathing new life into a languishing COBOL Virtual Machine™ (runtime), the Vision indexed file system, a source-level interactive application. ACUCOBOL-GT offers all of these debugger and nearly a dozen support utilities. capabilities and more. Our graphical technology allows you to create a native graphical user interface with the Screen Section and familiar COBOL verbs like DISPLAY and ACCEPT.
    [Show full text]
  • PL/I for AIX: Programming Guide
    IBM PL/I for AIX Programming Guide Ve r s i o n 2.0.0 SC18-9328-00 IBM PL/I for AIX Programming Guide Ve r s i o n 2.0.0 SC18-9328-00 Note! Before using this information and the product it supports, be sure to read the general information under “Notices” on page 309. Second Edition (June 2004) This edition applies to IBM PL/I for AIX 2.0.0, 5724-H45, and to any subsequent releases until otherwise indicated in new editions or technical newsletters. Make sure you are using the correct edition for the level of the product. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below. A form for readers’ comments is provided at the back of this publication. If the form has been removed, address your comments to: IBM Corporation, Department HHX/H1 555 Bailey Ave San Jose, CA, 95141-1099 United States of America 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. ©International Business Machines Corporation 1998,2004. All rights reserved. Contents Figures . vii COMPILE . .47 COPYRIGHT . .48 CURRENCY . .48 Part 1. Introducing PL/I on your DEFAULT . .48 workstation . .1 EXIT. .54 EXTRN . .54 Chapter 1. About this book . .3 FLAG . .55 FLOATINMATH. .55 Chapter 2. How to read the syntax GONUMBER . .56 GRAPHIC . .56 diagrams . .5 IMPRECISE . .56 INCAFTER . .57 Chapter 3.
    [Show full text]
  • Guide to Openvms File Applications
    Guide to OpenVMS File Applications Order Number: AA-PV6PD-TK April 2001 This document is intended for application programmers and designers who write programs that use OpenVMS RMS files. Revision/Update Information: This manual supersedes the Guide to OpenVMS File Applications, OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, AlphaServer, VAX, VMS, the Compaq logo Registered in U.S. and Patent and Trademark Office. Alpha, OpenVMS, PATHWORKS, DECnet, and DEC are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX and X/Open are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be the trademarks of their respective companies. Confidential computer software. Valid license from Compaq 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. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. ZK4506 The Compaq OpenVMS documentation set is available on CD-ROM.
    [Show full text]
  • Oral History of Roger Sippl
    Oral History of Roger Sippl Interviewed by: Luanne Johnson Recorded: December 13, 2005 and January 12, 2006 Mountain View, California CHM Reference number: X3655.2007 © 2005 Computer History Museum Table of Contents BACKGROUND AND THE DECISION TO MAJOR IN COMPUTER SCIENCE .............................. 3 EMPLOYMENT AT BECHTEL AND THE DECISION TO SEEK A JOB IN SILICON VALLEY....... 5 CROMEMCO AND DEVELOPING THE DESIGN FOR A RELATIONAL DATABASE..................... 8 FOUNDING RELATIONAL DATABASE SYSTEMS ............................................................................ 14 DECISION TO INCORPORATE SQL AND DEVELOPMENT OF INFORMIX 4GL ........................ 16 MERGER WITH INNOVATIVE SOFTWARE ........................................................................................ 20 PROBLEMS AFTER THE MERGER WITH INNOVATIVE.................................................................. 23 DECISION TO LEAVE INFORMIX AND SUBSEQUENT ACTIVITIES............................................. 25 PROMOTING UNIX................................................................................................................................... 28 SUPPORT SERVICES PROVIDED BY INFORMIX TO CUSTOMERS............................................ 30 Roger Sippl Conducted by The Information Technology Corporate Histories Project Abstract: In this interview, Roger Sippl describes his career prior to founding Relational Database Systems (later renamed to Informix) in 1980, including developing the design for the INFORMIX relational database management
    [Show full text]
  • Iscobol JISAM 100% Portable, Compact ISAM File System
    Datasheet isCOBOL JISAM 100% Portable, Compact ISAM File System Customers expect data access anytime on anyplace. With isCOBOL JISAM, your business can deliver fast and efficient access to COBOL ap- plications with ISAM data files anywhere Java technology runs, with- out the overhead of adding a relational database management system or investing in complex program change. Anytime, anywhere data access isCOBOL JISAM is a 100% Java-based indexed sequential access (ISAM) file system based on X/Open standards, opening up a wide range of different platforms, from mainframes to hand- held devices, for new and existing COBOL programs accessing ISAM data files. Highlights Using a B+ tree-index architecture, isCOBOL JISAM offers fast, self-balancing and flexible data • Written entirely in Java to run retrieval. With isCOBOL JISAM you can: anywhere the Java Runtime Environment (JRE) is supported, • Index a file with any number of indexes, each of which may include up to 16 non-con- including mobile devices An- tiguous segments. droid based. • Scan all or part of an index in ascending or descending order. • Includes built-in routines to • Use both unique keys and duplicate keys. perform basic file management • Simplify multi-language distributions and localization leveraging isCOBOL technology’s maintenance tasks support for Unicode. • Supports multi-language de- ployments The JUTIL utility is included with isCOBOL JISAM for basic file management. With JUTIL, devel- • Includes the ISMIGRATE utility opers can load and unload binary or line sequential files, compact files, check file consistency for simplified migration of data and rebuild isCOBOL JISAM files. files from other data sources Enable COBOL data access from Java • Includes the isCOBOL Graphical Veryant makes it easy for organizations to open vital COBOL data to new applications while Indexed File Editor (GIFE) utility continuing to leverage existing skill sets.
    [Show full text]
  • Enterprise PL/I for Z/OS Messages and Codes About This Book
    Enterprise PL/I for z/OS IBM Developer for z Systems PL/I for Windows IBM Messages and Codes Version 5 Release 2 GC27-8950-01 Enterprise PL/I for z/OS IBM Developer for z Systems PL/I for Windows IBM Messages and Codes Version 5 Release 2 GC27-8950-01 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page 163. First Edition (September 2017) | This edition applies to Version 5 Release 2 of Enterprise PL/I for z/OS (5655-PL5), and Version 9.1 of IBM Developer for z Systems (formerly IBM Rational Developer for System z) PL/I for Windows, and to any subsequent releases until otherwise indicated in new editions or technical newsletters. Make sure you are using the correct edition for the level of the product. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below. A form for readers' comments is provided at the back of this publication. If the form has been removed, address your comments to: IBM Corporation, Department H150/090 555 Bailey Ave. San Jose, CA, 95141-1099 United States of America 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 IBM Corporation 1999, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this book ..........
    [Show full text]
  • Universe User Reference Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Table of Contents Table of Contents
    C:\Program Files\Adobe\FrameMaker8\UniVerse 10.3\userref\Front February 5, 2009 11:04 am Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniVerse User Reference Version 10.3 February, 2009 C:\Program Files\Adobe\FrameMaker8\UniVerse 10.3\userref\Front February 5, 2009 11:04 am Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta IBM Corporation 555 Bailey Avenue San Jose, CA 95141 Licensed Materials – Property of IBM © Copyright International Business Machines Corporation 2008, 2009. All rights reserved. AIX, DB2, DB2 Universal Database, Distributed Relational Database Architecture, NUMA-Q, OS/2, OS/390, and OS/400, IBM Informix®, C-ISAM®, Foundation.2000 ™, IBM Informix® 4GL, IBM Informix® DataBlade® module, Client SDK™, Cloudscape™, Cloudsync™, IBM Informix® Connect, IBM Informix® Driver for JDBC, Dynamic Connect™, IBM Informix® Dynamic Scalable Architecture™ (DSA), IBM Informix® Dynamic Server™, IBM Informix® Enterprise Gateway Manager (Enterprise Gateway Manager), IBM Informix® Extended Parallel Server™, i.Financial Services™, J/Foundation™, MaxConnect™, Object Translator™, Red Brick® Decision Server™, IBM Informix® SE, IBM Informix® SQL, InformiXML™, RedBack®, SystemBuilder™, U2™, UniData®, UniVerse®, wIntegrate® are trademarks or registered trademarks of International Business Machines Corporation. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Windows, Windows NT, and Excel are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
    [Show full text]
  • Dcimfuser Guide
    DBMaker DCI MFCOBOL User's Guide Version: 5.1 Document No: 51/DBME51-T12302010-01-DMFC Author: DBMaster Support & production Team, Research & Development Division, SYSCOM Computer Engineering CO. Print Date: Nov 1 2011 Introduction Table of Content 1 Introduction ........................................................................................4 1.1 Additional Resources..................................................................................... 5 1.2 Technical Support .......................................................................................... 5 1.3 Document Conventions.................................................................................. 6 2 DCI for MFCOBOL ..............................................................................7 2.1 DCI for MFCOBOL Overview......................................................................... 7 File System and Databases......................................................................................................... 7 Relation Chart .............................................................................................................................. 8 System Requirements.................................................................................................................. 8 2.2 Setup Instructions .......................................................................................... 9 Install Net Express 5.1 ............................................................................................................... 9 Install
    [Show full text]
  • Tun SQL – Data Access Tun Plus 2009 Issued May 2008
    Tun SQL – Data Access Tun Plus 2009 Issued May 2008 Copyright © 1989-2008 Esker S.A. All rights reserved. © 1998-2002 The OpenSSL Project; © 1994-2003 Sun Microsystems, Inc.; © 1996 Wolfgang Platzer ([email protected] graz.ac.at); © 1995-1998 Eric Young ([email protected]). All rights reserved. Tun contains components which are derived in part from OpenSSH software. See the copyright.txt file on the Tun CD for additional copyright notices, conditions of use and disclaimers. Use and duplicate only in accordance with the terms of the Software License Agreement - Tun Products. North and South American distributions of this manual are printed in the U.S.A. All other distributions are printed in France. Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means without the prior written consent of Esker S.A.. Esker S.A., 10 rue des Émeraudes, 69006 Lyon, France Tel: +33 (0)4.72.83.46.46 ♦ Fax: +33 (0)4.72.83.46.40 ♦ [email protected] ♦ www.esker.fr Esker, Inc., 1212 Deming Way, Suite 350, Madison, WI 53717 USA Tel: +1.608.828.6000 ♦ Fax: +1.608.828.6001 ♦ [email protected] ♦ www.esker.com Esker Australia Pty Ltd. (Lane Cove - NSW) ♦ Tel: +61 (0)2 8596 5100 ♦ [email protected] ♦ www.esker.com.au Esker GmbH (München) ♦ Tel: +49 (0) 89 700 887 0 ♦ [email protected] ♦ www.esker.de Esker Italia SRL (Milano) ♦ Tel: +39 02 57 77 39 1 ♦ [email protected] ♦ www.esker.it Esker Ibérica, S.L.
    [Show full text]
  • VSI COBOL DBMS Database Programming Manual
    VSI OpenVMS VSI COBOL DBMS Database Programming Manual Document Number: XX-XXXXXX-XXX Publication Date: month 2018 This manual explains how to develop Oracle DBMS database programs with VSI COBOL on the OpenVMS Alpha, OpenVMS I64, and the OpenVMS VAX operating systems. Revision Update Information: This is a new manual. Operating system and Version: VSI OpenVMS Version X.X Software Version: VSI COBOL Version X.X VMS Software, Inc., (VSI) Bolton, Massachusetts, USA VSI OpenVMS VSI COBOL DBMS Database Programming Manual: Copyright © 2018 VMS Software, Inc., (VSI), Bolton Massachusetts, USA Legal Notice Confidential computer software. Valid license from VSI 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 VSI 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. VSI shall not be liable for technical or editorial errors or omissions contained herein. HPE, HPE Integrity, HPE Alpha, and HPE Proliant are trademarks or registered trademarks of Hewlett Packard Enterprise. UNIX is a registered trademark of The Open Group. Oracle is a registered trademark of Oracle and/or its affiliates. The VSI OpenVMS documentation
    [Show full text]
  • Unit 8 Data Structures and File Organization
    Data Structures and File UNIT 8 DATA STRUCTURES AND Organization FILE ORGANIZATION Structure 8.0 Objectives 8.1 Introduction 8.2 Definitions and Basic Concepts 8.2.1 Memory Hierarchy 8.2.2 RAID Technology 8.2.3 Indexes 8.2.4 Binary Search 8.3 Data Structures 8.3.1 Linked Lists 8.3.2 Inverted Lists 8.3.3 B-Trees 8.4 Files and their Organizations 8.4.1 File Storage Concepts 8.4.2 Sequential Access Method (SAM) 8.4.3 Indexed Sequential Access Method (ISAM) 8.4.4 Direct Access Method (DAM) 8.5 Summary 8.6 Answers to Self Check Exercises 8.7 Keywords 8.8 References and Further Reading 8.0 OBJECTIVES The database concept is an important aspect of the storage and retrieval of information. Data structure and file organization are concerned with methods of organization of data in a database dealing with physical organization of data. After reading this Unit, you will be able to: l understand the basic concepts related to data structures and file organization. l comprehend physical storage structures of data and file organization techniques. l gain an insight into the role which the data structures and file organization play in the overall performance and access efficiency in a database. 8.1 INTRODUCTION Data structures and file organization refer to the methods of organizing the data in a database. They primarily deal with physical storage of data which assumes significance in retrieving, storing and reorganizing data in a database. 129 Data Models and Database The performance of a database greatly depends on the data storage structures and Design file organization.
    [Show full text]