Skip to content
Padhora
Sign in
BrowsePlans

DI03016041 · Semester 3 · 5G scheme

Database Management

Notes and solutions following the Gujarat Technological University (GTU) syllabus for DI03016041. Independent material — not issued by the university.

Information Technology

Materials

Syllabus

The official syllabus this material follows.

  • Syllabus

    9 pages

    FreeRead

Complete Book

The whole syllabus, unit by unit, written for the exam.

Problem Solver

Step-by-step solutions to typical problems.

Slides

Lecture slides for revision.

PYQ Solutions

Past university papers, fully solved.

  • Solved past papers — detailed answers

    28 pages · English + ગુજરાતી

    Premium Preview · 3 pages

Syllabus units

Unit 1: Introduction to Database Systems
  • 1.1 Introduction
  • 1.1.1 Data and Information
  • 1.1.2 Database and Database Management System
  • 1.1.3 Purpose of Database System and Application
  • 1.1.4 Metadata
  • 1.1.5 Data items, fields & records
  • 1.1.6 Data Dictionary
  • 1.2 File oriented System versus database system
  • 1.3 Database Administrator
  • 1.3.1 Roles and responsibilities of DBA
  • 1.4 Schema, Sub-Schema, Instances
  • 1.5 Data Abstraction
  • 1.5.1 Internal Level
  • 1.5.2 Conceptual Level
  • 1.5.3 External Level
  • 1.6 Data Independence
Unit 2: Entity Relationship Model
  • 2.1 Basic concepts of E-R
  • 2.1.1 Entity
  • 2.1.2 Attributes
  • 2.1.3 Relationship
  • 2.1.3.1 Participation
  • 2.1.3.2 Recursive relationships
  • 2.1.3.3 Degree of relationship set
  • 2.2 Mapping Cardinality
  • 2.3 ER Diagrams
  • 2.4 Weak Entity Sets
  • 2.5 Enhanced ER Model
  • 2.5.1 Subclass & Super Class
  • 2.5.2 Generalization
  • 2.5.3 Specialization
  • 2.5.4 Aggregation
  • 2.6 Converting ER Diagrams to database
Unit 3: Structured Query Language
  • 3.1 Introduction and basic commands
  • 3.1.1 SQL Data types
  • 3.1.2 Data Definition Language Commands : create, alter, truncate and drop
  • 3.1.3 Data Manipulation Language Commands: insert, update and delete
  • 3.1.4 Data query Language: select
  • 3.1.5 Privilege command : grant and revoke
  • 3.1.6 Other Miscellaneous: describe, distinct, order by, group by and having
  • 3.2 SQL Views
  • 3.3 SQL Functions
  • 3.4 SQL Operators
  • 3.5 Set Operators: union, union all, intersect and minus
  • 3.6 Joins
  • 3.7 SQL Constraints
  • 3.7.1 Need of Constraints
  • 3.7.2 Domain Integrity constraints: Not null and Check
  • 3.7.3 Entity Integrity constraints: Unique, Primary key,
  • 3.7.4 Referential integrity Constraints: Foreign key, Reference key
Unit 4: Normalization
  • 4.1 Anomalies created by poor database design
  • 4.2 Normalization
  • 4.2.1 Definition and its importance
  • 4.2.2 Goals of Normalization
  • 4.3 Functional Dependencies
  • 4.3.1 Prime Vs Non-Prime Attributes
  • 4.3.2 Functional Dependency
  • 4.3.2.1 Partial Functional Dependency
  • 4.3.2.2 Full Functional Dependency
  • 4.3.2.3 Transitive Dependency
  • 4.4 Normal Forms
  • 4.4.1 First Normal Form
  • 4.4.2 Second Normal Form
  • 4.4.3 Third Normal Form
  • 4.4.4 Boyce Codd Normal Form
Unit 5: Transaction Management
  • 5.1 Basic Transaction Concepts
  • 5.1.1 Definition
  • 5.1.2 State transition diagram
  • 5.1.3 ACID Properties
  • 5.1.4 Transaction Log
  • 5.2 Concurrency Control
  • 5.2.1 Definition
  • 5.2.2 Problems of Concurrency Control
  • 5.2.3 Schedule and its types
  • 5.3 Serializability of transactions
  • 5.4 Locking methods for Concurrency Control

About this course

Database management course introduces students to database design using various models, SQL commands, techniques, and operation. This helps students to design ER-models to represent simple databases and convert them into relational tables, populate relational databases and formulate SQL queries on data. Students will improve database design through normalization. Students will understand how database systems must provide for the safety of the stored information, despite system crashes or attempts at unauthorized access. If data are to be shared among several users, the system must avoid possible anomalous results due to multiple users concurrently accessing the same data.