GATEDatabases
Databases for GATE
~8 marks — nearly every question is mechanical once the right procedure is chosen.
📊 ~5 Q · ~8 marks (8% of the paper)🗄️
How toppers play this section
Databases is the most procedural subject in the paper: almost every question has a fixed method, and the marks go to whoever applies it without slipping. Candidate key finding and highest-normal-form identification appear almost every year, and both depend on computing attribute closures correctly and finding every candidate key rather than just one. SQL questions concentrate on where theory and practice diverge, namely set versus multiset semantics and three-valued logic with nulls, which is where the NOT IN trap lives. B-plus tree order computation is a near-certain numerical and hinges on computing the internal and leaf orders separately. Serializability is decided by a precedence graph cycle check, which takes a minute and cannot go wrong if the conflicting pairs are listed item by item.
Chapters
Built to the GATE blueprint — notes, shortcuts, solved PYQ-style examples and practice in every chapter.
Topic-wise weightage in GATE
Expected question counts from previous-year paper analyses. Topics with an arrow already have a full chapter.
| Topic | GATE CS — single 3-hour CBT paper Q | Score used for M.Tech admission / PSU recruitment Q | Priority |
|---|---|---|---|
| ER Model & Relational Model | ~1 | Medium | |
| Relational Algebra, Tuple Calculus & SQL | ~1-2 | High | |
| Integrity Constraints & Normal Forms | ~2 | Very high | |
| File Organization & Indexing (B and B+ Trees) | ~1-2 | Very high | |
| Transactions & Concurrency Control | ~2 | Very high |
Take the next step
GATE Databases — find a tutor
Pair self-study with a tutor, a live course or a coaching centre.