students and freshers learning database fundamentals

DBMS Basics — the concepts interviewers actually check for

Database Management System (DBMS) questions in exams and interviews tend to circle back to a small set of core ideas. Understanding these deeply is more valuable than memorising every SQL syntax variant.

Keys — how rows are uniquely identified and linked

A primary key uniquely identifies each row in a table. A foreign key in one table references a primary key in another, creating a relationship between tables — this is the foundation of how relational databases connect data without duplicating it.

Normalization — reducing redundancy

Normalization organises data to minimise duplication and avoid update anomalies. First Normal Form (1NF) removes repeating groups, 2NF removes partial dependencies, 3NF removes transitive dependencies — each level solves a specific kind of redundancy problem.

ACID properties — what makes a transaction reliable

Atomicity (all-or-nothing), Consistency (valid state to valid state), Isolation (concurrent transactions don't interfere), and Durability (committed changes survive failures) — together these guarantee that database transactions behave predictably even under failures or concurrent access.

Joins — combining data across tables

An INNER JOIN returns only matching rows from both tables. A LEFT JOIN returns all rows from the left table plus matches from the right (with NULLs where there's no match). Knowing which join type to use is a very common practical interview check.

Examples

A Students table and a Courses table linked by a StudentID foreign key is a classic one-to-many relationship.
Storing a student's multiple phone numbers in one comma-separated column violates 1NF — it should be a separate related table.
A bank transfer failing halfway through and still deducting money from one account would violate Atomicity.

Common mistakes

Memorising normal-form definitions without being able to normalise an actual example table.
Confusing INNER JOIN and LEFT JOIN results, especially when rows have no match.
Describing ACID properties in the wrong order or conflating Consistency with Isolation.

Try it yourself

Table A has 3 rows, Table B has 2 matching rows and 1 non-matching row for a LEFT JOIN from A to B. How many rows appear in the result if every A row has exactly one match in B?

Show answer

3 rows — a LEFT JOIN keeps every row from the left table (A), so all 3 appear, each paired with its match (or NULL if unmatched).

Frequently asked questions

Do I need to memorise SQL syntax for interviews?

Basic SELECT/JOIN/WHERE syntax is commonly expected, but concept understanding (why a join or a normal form is needed) usually matters more than syntax recall.

Can Learn2Plus AI show a normalization example step by step?

Yes — ask for a step-by-step normalization walkthrough with a small example table.

Can I get DBMS interview-style practice questions?

Yes — ask for DBMS interview practice and you'll get one question at a time with feedback.

Practice DBMS concepts with Learn2Plus AI

Try 2 lessons free — no card required.