UNIT 1 Lesson-1 Introduction to Database Management System Hi!

In this chapter you will learn about the need and features of a Data Base Management System What is a Database? Have you ever thought of what exactly is a database? A database is a collection of information or data organized and presented to serve a specific purpose. (You could take the example of a telephone book as a common database.) A computerized database is an updated, organized file of machine readable information that is rapidly searched and retrieved by computer. Data are binary computer representations of stored entities. Data can exist in many forms. Data can be defined in many ways. Information science defines data as unprocessed information. Data is converted into information, and information is converted into knowledge. For the purposes of Enterprise, data is a small unit of information, i.e. a learner's name or an exam mark. What is a DBMS? Database Management System is a collection of computer programs that allow storage, modification, and extraction of information from a database. There are many different types of DBMSs, ranging from small systems that run on personal computers to huge systems that run on mainframes. The following are examples of database applications: computerized library systems, automated teller machines, flight reservation systems, computerized parts inventory systems MGI. The examples of DBMS are MS-ACCESS, ORACLE, SQL SERVER etc. Why a DBMS? You may think how a DBMS would help in the management of a Database? The reasons for that are, a DBMS is capable of 1. Providing data independence and efficient access of data. 2. Reducing the application development time. 3. Providing Data integrity and security. 4. Uniform data administration 1

UNIT 1 Files vs. DBMS Application must stage large datasets between main memory and secondary storage (e.g., buffering, page-oriented access, 32-bit addressing, etc.). There is a need to protect data from inconsistency due to multiple concurrent users. Crash recovery, security and access control should be taken into account. Database management systems were developed to handle the following difficulties of typical file-processing systems supported by conventional operating systems. Data redundancy and inconsistency Difficulty in accessing data Data isolation - multiple files and formats Integrity problems Atomicity of updates Concurrent access by multiple users Security problems

A database management system is a software that provides services for accessing a database, while maintaining all the required features of data. The major components of a DBMS are the following: Transaction management: A transaction is a sequence of database operations that represents a logical unit of work and that accesses a database and transforms it from one state to another. Concurrency Control: This is the database management activity of coordinating the actions of database manipulation processes that operate concurrently that access shared data and potentially interfere with one another Recovery Management: This in a database ensures the aborted or failed transactions create no adverse effects on the database or the other transactions Security Management: Refers to the protection of data against un-authorized access Language Interface: The DBMS provides support languages for definition and manipulation of data in the database. Storage Management: The DBMS provides a mechanism for management of permanent storage of the data.

UNIT 1 Characteristics of Data in a Database You may be interested to know the characteristics of data in a Database. They are, 1. Shared - Data in database are shared among Different users and applications. 2. Persistence Data in a database exist permanently in the sense that data can live beyond the scope of the process that created it. 3. Correctness Data should be correct 4. Security Data should be protected from Un-Authorized access. 5. Consistency- Whenever more than one data element in a database represents real-world values, the values should be protected from unauthorized access. 6. Non-redundancy No two data items in a database should represent the same real world entity. TYPES OF DATABASE MANAGEMENT SYSTEMS A DBMS can take any one of the several approaches to manage data. Each approach constitutes a database model. A data model is a collection of descriptions of data structures and their contained fields, together with the operations or functions that manipulate them. A data model is a comprehensive scheme for describing how data is to be represented for manipulation by humans or computer programs. A thorough representation details the types of data, the topological arrangements of data, spatial and temporal maps onto which data can be projected, and the operations and structures that can be invoked to handle data and its maps. The various Database Models are the following: Relational data model based on tables. Network data model based on graphs with records as nodes and relationships between records as edges. Hierarchical data model based on trees. Object-Oriented data model based on the object-oriented programming paradigm.

Relational Model A database model that organizes data logically in tables. A formal theory of data consisting of three major components: (a) A structural aspect, meaning that data in the database is perceived as tables, and only tables, (b) An integrity aspect, meaning that those tables satisfy certain 3

UNIT 1 integrity constraints, and (c) A manipulative aspect, meaning that the tables can be operated upon by means of operators which derive tables from tables. Here each table corresponds to an application entity and each row represents an instance of that entity. (RDBMS - relational database management system) A database based on the relational model was developed by E.F. Codd. A relational database allows the definition of data structures, storage and retrieval operations and integrity constraints. In such a database the data and relations between them are organized in tables. A table is a collection of records and each record in a table contains the same fields. Properties of Relational Tables: Values Are Atomic Each Row is Unique Column Values Are of the Same Kind The Sequence of Columns is Insignificant The Sequence of Rows is Insignificant Each Column Has a Unique Name

Certain fields may be designated as keys, which mean that searches for specific values of that field will use indexing to speed them up. Often, but not always, the fields will have the same name in both tables. For example, an "orders" table might contain (customer-ID, product-code) pairs and a "products" table might contain (product-code, price) pairs so to calculate a given customer's bill you would sum the prices of all products ordered by that customer by joining on the product-code fields of the two tables. This can be extended to joining multiple tables on multiple fields. Because these relationships are only specified at retrieval time, relational databases are classed as dynamic database management system. The RELATIONAL database model is based on the Relational Algebra. Advantages Structural Independence Conceptual Simplicity Ease of design, implementation, maintenance and usage. Ad hoc query capability Hardware Overheads Ease of design can lead to bad design

Disadvantages

UNIT 1 Network Model The popularity of the network data model coincided with the popularity of the hierarchical data model. Some data were more naturally modeled with more than one parent per child. So, the network model permitted the modeling of many-to-many relationships in data. In 1971, the Conference on Data Systems Languages (CODASYL) formally defined the network model. The basic data modeling construct in the network model is the set construct. A set consists of an owner record type, a set name, and a member record type. A member record type in the Network Model can have that role in more than one set; hence the multiparent concept is supported. An owner record type can also be a member or owner in another set. The data model is a simple network, and link and intersection record types (called junction records by IDMS) may exist, as well as sets between them . Thus, the complete network of relationships is represented by several pair wise sets; in each set some (one) record type is owner (at the tail of the network arrow) and one or more record types are members (at the head of the relationship arrow). Usually, a set defines a 1:M relationship, although 1:1 is permitted. The CODASYL network model is based on mathematical set theory.

NETWORK DATA MODEL Advantages Conceptual Simplicity Ease of data access Data Integrity and capability to handle more relationship types Data independence Database standards 5

UNIT 1 Disadvantages System complexity Absence of structural independence

Hierarchical Model The hierarchical data model organizes data in a tree structure. There is a hierarchy of parent and child data segments. This structure implies that a record can have repeating information, generally in the child data segments. Data in a series of records, which have a set of field values attached to it. It collects all the instances of a specific record together as a record type. These record types are the equivalent of tables in the relational model, and with the individual records being the equivalent of rows. In a Hierarchical model you could create links between these record types; the hierarchical model uses Parent Child Relationships. These are a 1: N mapping between record types. This is done by using trees, like set theory used in the relational model, "borrowed" from maths. For example, an organization might store information about an employee, such as name, employee number, department, salary. The organization might also store information about an employee's children, such as name and date of birth. The employee and children data forms a hierarchy, where the employee data represents the parent segment and the children data represents the child segment. If an employee has three children, then there would be three child segments associated with one employee segment. In a hierarchical database the parent-child relationship is one to many. This restricts a child segment to having only one parent segment. Hierarchical DBMSs were popular from the late 1960s, with the introduction of IBM's Information Management System (IMS) DBMS, through the 1970s.

UNIT 1 Advantages Simplicity Data Security and Data Integrity Efficiency Implementation Complexity Lack of structural independence Programming complexity

Disadvantages

Object Oriented Data Models Object DBMSs add database functionality to object programming languages. They bring much more than persistent storage of programming language objects. Object DBMSs extend the semantics of the C++, Smalltalk and Java object programming languages to provide fullfeatured database programming capability, while retaining native language compatibility. A major benefit of this approach is the unification of the application and database development into a seamless data model and language environment. As a result, applications require less code, use more natural data modeling, and code bases are easier to maintain. Object developers can write complete database applications with a modest amount of additional effort. In contrast to a relational DBMS where a complex data structure must be flattened out to fit into tables or joined together from those tables to form the in-memory structure, object DBMSs have no performance overhead to store or retrieve a web or hierarchy of interrelated objects. This one-to-one mapping of object programming language objects to database objects has two benefits over other storage approaches: it provides higher performance management of objects, and it enables better management of the complex interrelationships between objects. This makes object DBMSs better suited to support applications such as financial portfolio risk analysis systems, telecommunications service applications, World Wide Web document structures, design and manufacturing systems, and hospital patient record systems, which have complex relationships between data. Advantages Capability to handle large number of different data types Marriage of object-oriented programming and database technology 7

UNIT 1 Data access Difficult to maintain Not suited for all applications

Disadvantages

Check Your Progress!! 1. What do you mean by data? 2. Define what is a DBMS? 3. What are the characteristics of data in a database? 4. What are the advantages of using a DBMS? 5. What are the different types of Data Models? 6. What is the major difference between Network data model and the Hierarchical data model? Activities Pick the various Databases which you are very much familiar with. And identify the data model that suits those databases. References

http://www.tc.cornell.edu/services/edu http://www.unixspace.com/context/databases.html Date, C.J., Introduction to Database Systems (7th Edition) Addison Wesley, 2000 Leon, Alexis and Leon, Mathews, Database Management Systems, LeonTECHWorld.