Database Management System — What This Subject Is About
Three units carry three quarters of this paper — Units 2, 3 and 4 are 25% each, 75% between them — and they are one story told in three parts: how data is modelled (Unit 2), how the relational model works (Unit 3), and how tables are designed so they do not repeat or contradict themselves (Unit 4). Database Management System is the subject that teaches you to design a database properly before a single row is stored.
The subject covers five units in 42 periods: an introduction to database systems; data models and keys; the relational model; relational database design; and SQL with MySQL. The paper is a pure theory paper — 60 marks external in 3 hours, with 40 internal marks. The lab that goes with it, Database Management System (Lab), is a separate practical subject with its own syllabus and its own 100 marks.
Subject 3.2 (Theory) • Total 100 Marks • 3 Credits • L 3 – P 0 • 3rd Semester — Information Technology • Session 2026–27

What You Will Study
Unit 1 — Introduction (6 Periods, 10%)
Database system concepts and architecture, components of DBMS, table structure, schema definition, three views of data (external view, conceptual view, internal view).
What a database system is and how it is put together — its components, what a schema is, and the three views of data: what the user sees, what the designer defines, and how it is stored.
Unit 2 — Data Model and Keys (8 Periods, 25%)
Define data model; data models: network model, hierarchical model, E-R model; advantages and disadvantages of each data model; concept of keys (primary, candidate, super, foreign); constraints; strong entity set and weak entity set.
How data is modelled before any table is made — the three data models, the E-R model with entities and relationships, and keys: the columns that identify each row.
Unit 3 — Relational Model (10 Periods, 25%)
The relational data model and relational database constraints; ER/EER to relational model mapping; relational algebra and relational calculus; relational algebra (basic operations: union, intersection, difference and Cartesian product); additional relational algebraic operations (projection, selection of rows, division, rename and join).
The relational model itself — how an E-R diagram becomes tables, the constraints that keep tables honest, and relational algebra: the operations (select, project, join and the rest) that SQL is built on.
Unit 4 — Relational Database Design (10 Periods, 25%)
Functional dependencies and normalization for relational databases; types of normalization (1NF, 2NF, 3NF, multivalued dependencies and BCNF, Fourth Normal Form, Fifth Normal Form).
How to design tables that do not repeat data or contradict themselves — functional dependencies and normalization, from 1NF up to 5NF, with BCNF in between.
Unit 5 — SQL/MySQL (8 Periods, 15%)
MySQL data types; data definition commands; data manipulation commands; data retrieval commands; types of operators — arithmetic, comparison and logical operators.
The working language: SQL in MySQL — creating tables, inserting, updating and deleting rows, retrieving data with SELECT, and the operators that filter it.
Complete Syllabus
The full examination scheme, the unit-wise marks distribution and the reference books from the official syllabus. The unit-wise topics are in the “What You Will Study” section above.
Examination Scheme
| Code | Paper | Type | L – P | Credits | Internal | External | Total |
|---|---|---|---|---|---|---|---|
| 3.2 | Database Management System | Theory | 3 – 0 | 3 | Theory 40 | Theory 60 (3 hrs) | 100 |
| Database Management System Total | 3 | 40 | 60 | 100 | |||
Units at a Glance
| Unit | Topic | Periods | Marks (%) |
|---|---|---|---|
| 1 | Introduction | 6 | 10 |
| 2 | Data Model and Keys | 8 | 25 |
| 3 | Relational Model | 10 | 25 |
| 4 | Relational Database Design | 10 | 25 |
| 5 | SQL/MySQL | 8 | 15 |
| Total | 42 | 100 | |
Total: 42 periods, 100%. The percentages are the suggested distribution of marks in the official syllabus, out of the 60-mark external theory paper. Units 2, 3 and 4 together carry three quarters of the paper.
Course Outcomes
- CO1: Describe fundamentals of DBMS, its installation and working.
- CO2: Understand the concept of keys and various data model.
- CO3: Understand relational model and relational algebraic operations.
- CO4: Designing a Relational Database.
- CO5: Apply SQL commands to create, insert, retrieve, update, delete data from the Relational databases.
Reference Books
As listed in the syllabus:
- Fundamentals of Database Systems — Elmasri and Navathe, Pearson Education.
- Database Management Systems — Raghu Ramakrishnan and Johannes Gehrke, Tata McGraw-Hill, New Delhi, India.
- Database System Concepts — Abraham Silberschatz, Henry F. Korth and S. Sudarshan, McGraw-Hill, New Delhi, India.
- Introduction to Database Systems — C. J. Date, Pearson Education.
- Introduction to SQL — Rick F. van der Lans, Pearson Education.
How to Prepare for Database Management System
Draw E-R diagrams by hand, with keys marked. Unit 2 is where most students lose marks they should not lose: an E-R diagram without keys, without cardinalities, or with a weak entity drawn as a strong one. Practise on small cases — a library, a college, a shop — and mark the primary key of every entity and the cardinality of every relationship before you convert anything to tables.
Treat relational algebra as a toolkit, not a list. Select, project, join, union, difference, division — each operation does one job, and a query is a chain of them. Work the operations on tiny tables (three rows, three columns) until you can see what each one returns. The theory paper asks you to write expressions; the lab asks you to write the same logic in SQL.
Do normalization step by step, in writing. List the functional dependencies first, find the candidate keys, then walk 1NF, 2NF, 3NF and BCNF one step at a time, writing down what changes at each step. Students in my class always mix up 2NF and 3NF: 2NF removes partial dependency (part of the key deciding a non-key attribute), 3NF removes transitive dependency (a non-key attribute deciding another non-key attribute). Keep that one sentence straight and the rest follows.
Write SQL, do not just read it. Unit 5 is only 15% of the theory paper, but SQL is the whole of the lab. Write every query yourself — CREATE TABLE, INSERT, SELECT with WHERE, GROUP BY and HAVING, JOINs — and run it. A query you have run and fixed is worth ten you have only read.
Finish with timed practice. Work through model papers in one sitting of 3 hours, without notes — exactly like the real examination. Then compare your answers with the model answer outline and note the points you missed. Questions that repeat across sets are the subject's most important questions.
Exam Tips
- Attempt all five questions. The paper pattern gives three parts (a), (b) and (c) in each question, of which any two are to be answered — pick the two parts you know best in every question, and do not leave any question blank.
- Mark keys and cardinalities on every E-R diagram. An E-R diagram without a primary key on each entity and a cardinality on each relationship is incomplete, however neat it looks.
- Show every step of normalization. Write the functional dependencies, the candidate keys, and what changes at each normal form. Examiners give marks for the steps even if the final tables have a small slip.
- Write SQL exactly. One wrong keyword or one missing comma breaks a query. In the exam, write the query, then read it back slowly as if you were the database running it.
- Manage the 3 hours. About 35 minutes per question leaves a few minutes at the end to re-read your answers. Do not spend an hour on one favourite question.
- Write in your own words, in the same order as the questions. Short, clear points with the key terms score better than long copied paragraphs.
Frequently Asked Questions
How many marks is Database Management System worth in the 3rd semester?
100 marks in total and 3 credits: internal assessment 40 marks (theory) and external theory paper 60 marks in 3 hours.
Which units carry the most marks in DBMS?
Units 2 (Data Model and Keys), 3 (Relational Model) and 4 (Relational Database Design) carry 25% each — three quarters of the paper between them. Unit 1 is the lightest at 10%; Unit 5 (SQL/MySQL) carries 15%. The complete unit-wise table is in the Complete Syllabus section above.
Is there a practical or lab for DBMS?
Yes — Database Management System (Lab), subject 3.6, is a separate practical subject with 6 experiments and 4 SQL case studies (Library, Employee, Bookstore, Student Grades), worth 100 marks (60 internal + 40 external practical). It has its own syllabus post on this site.
What are the most scoring topics in DBMS?
Normalization (worked step by step from functional dependencies) and relational algebra expressions are the most scoring, because a correct method earns marks step by step. E-R diagrams with keys and cardinalities marked, and correctly written SQL, are the next best scorers.
Which books should I refer to for DBMS?
The syllabus lists 5 books, including Fundamentals of Database Systems by Elmasri and Navathe and Database System Concepts by Silberschatz, Korth and Sudarshan. The full list is in the Complete Syllabus section above.
What is the paper pattern for DBMS?
The board's last published pattern is 5 questions with three parts (a), (b) and (c) each, of which any two parts are to be answered per question. The 2026-27 format has not been published separately, so prepare on this pattern and confirm with your polytechnic.
How can I download the DBMS syllabus PDF?
The PDF is free to download — use the download link in the Download section below. It is prepared by KAMALDNP from the official BTEUP syllabus.
Related Syllabus Posts
- Operating Systems — BTEUP IT 3rd Semester Syllabus 2026-27
- Software Engineering — BTEUP IT 3rd Semester Syllabus 2026-27
- Web Technologies — BTEUP IT 3rd Semester Syllabus 2026-27
- Computer Programming Using C — BTEUP IT 3rd Semester Syllabus 2026-27
- Operating Systems (Lab) — BTEUP IT 3rd Semester Syllabus 2026-27
- Database Management System (Lab) — BTEUP IT 3rd Semester Syllabus 2026-27
- Summer Internship-I — BTEUP IT 3rd Semester Syllabus 2026-27
- All BTEUP Syllabus Posts — kamaldnp.com Blog
- KAMALDNP Books — Short Notes, Question Banks & Practice Sets
Notes, Question Bank & Practice Sets — Database Management System
The syllabus PDF on this page stays 100% FREE — no login, no payment, always. The study material below is a paid KAMALDNP product: buy once for just ₹10 and you get both the Hindi and English PDFs. Every PDF is generated with your name and enrolment number and is password-locked, so it remains personal to you. After purchase, the PDF is also sent to your email, and it is always available for download on the My Downloads page.
Unit-wise short revision notes prepared from the official BTEUP 2026-27 syllabus of this subject.
Buy / Download — My DownloadsOne original practice (model) paper with a model-answer outline. This is a KAMALDNP practice paper — NOT a BTEUP board paper, and no question in it is promised to appear in your exam.
Buy / Download — My Downloads10 Practice Sets — practice/guess sets only (no verified previous-year board papers available for this subject yet)
Buy / Download — My DownloadsAlready purchased? You will find the Download button on the same My Downloads page — you will not be charged again.
Download the Database Management System Syllabus PDF
Download the complete Database Management System syllabus PDF below — prepared by KAMALDNP, with the full topic list, examination scheme and reference books.
Download the Database Management System Syllabus PDF
Source: BTEUP IRDT Kanpur NEP-2020 curriculum for Diploma in Information Technology, effective session 2026-27 (urise.up.gov.in). Topic lists follow the official syllabus; short explanations are the author's own plain-English summaries, not syllabus text. Please confirm with your own polytechnic for any local changes.
Comments (0)
Share your question or experience about this syllabus. Your comment will appear after review.
No comments yet — be the first to share your thoughts!