What makes DBMS a scoring paper
Database Management Systems (BCS402 in AKTU and equivalent codes in other universities) has one of the most predictable examination patterns in the entire B.Tech CSE programme. Unlike algorithms or operating systems where the examiner can ask a variety of problem types, DBMS papers draw from a narrow, well-defined set of question types: ER diagram design, relational algebra expressions, SQL queries, normalisation (1NF, 2NF, 3NF, BCNF), and transaction management (serialisability, locking). Once you have practised each of these six question types, you have prepared for virtually the entire paper.
Unit-by-unit breakdown and what to prioritise
Here is the realistic priority order for DBMS preparation based on five years of Indian university papers:
- Unit 4 — Functional Dependencies and Normalisation: The highest-weight topic in nearly every university. 1NF, 2NF, 3NF, and BCNF decomposition with examples appear in every paper. You must be able to identify functional dependencies, find candidate keys, and carry out decomposition step by step.
- Unit 3 — SQL, Constraints, Views and PL/SQL: SQL query writing (SELECT with WHERE, GROUP BY, HAVING, JOINs, subqueries) is asked as at least one 10-mark question in every paper. Practice writing queries from an English description — this is exactly what the examiner asks.
- Unit 1 — Database Concepts, Architecture and ER Modelling: ER diagram drawing is a consistent 10-mark question. Know the exact notation: rectangles for entities, ellipses for attributes, diamonds for relationships, double ellipses for multi-valued attributes.
- Unit 2 — Relational Model, Relational Algebra and Calculus: Relational algebra expressions (SELECT σ, PROJECT π, JOIN ⋈, UNION ∪, DIFFERENCE −) are asked in at least one question. Write the expression using the correct symbols.
- Unit 5 — Transactions, Concurrency Control and Recovery: Transaction serializability and conflict/view serializability tests are the main questions. Two-phase locking protocol and ACID properties are frequent short questions.
The ER diagram — how to never lose marks on it
ER diagram questions are typically 10 marks. Examiners award marks for: (a) correctly identifying entities and attributes, (b) correctly showing relationships with cardinality (1:1, 1:M, M:N), (c) identifying primary keys for each entity (underline the attribute), and (d) showing weak entities with double rectangles. The most common mistakes are drawing relationship lines without cardinality labels, and confusing attributes with entities.
Exam technique
When you read the question, underline every noun — each noun is usually either an entity or an attribute. Underline every verb — each verb is usually a relationship. This simple technique covers 90% of ER diagram questions.
SQL query writing — the method that works in exams
SQL questions ask you to write a query given a description like 'Find the names of all students who scored more than 80 in Mathematics'. The method: (1) identify the table(s) involved, (2) identify the output columns (SELECT), (3) identify the filter conditions (WHERE), (4) check if any grouping is needed (GROUP BY / HAVING), (5) check if multiple tables need joining (JOIN or subquery). Write the query clause by clause, not all at once.
- SELECT column list FROM table — always start here
- WHERE condition — add filters
- JOIN table ON condition — add when you need data from multiple tables
- GROUP BY column — add when the question asks for aggregates (count, sum, average) per category
- HAVING condition — add filters on grouped results (like 'departments with more than 5 employees')
- ORDER BY column ASC/DESC — add when the question asks for results 'in order'
Normalisation — the step-by-step method for full marks
Normalisation questions ask you to decompose a relation to a given normal form. The correct answer always includes: the relation schema, all functional dependencies, the candidate keys, and then the decomposition with justification at each step. A correct final answer with no justification typically earns 4 of the 10 available marks. Showing the violations at each stage and justifying why the decomposition resolves them earns the remaining 6 marks.
Normalisation shortcut test
1NF check: No repeating groups or multi-valued attributes. 2NF check: No partial dependencies (every non-key attribute must depend on the WHOLE primary key). 3NF check: No transitive dependencies (non-key attributes must not depend on other non-key attributes). BCNF check: Every determinant must be a candidate key.
Three weeks before the exam — the revision plan
Week 1: Cover ER diagrams and normalisation — draw five ER diagrams from previous papers and decompose five relations to BCNF. Week 2: Practise SQL — write twenty queries from previous paper questions without looking at notes, then check. Week 3: Cover relational algebra, transactions, and revise all previous material. On the day before the exam: read only your own summary notes, never a new chapter.