Changing Data for SQLs
Changing data in SQL means writing to tables with INSERT, UPDATE and DELETE, and protecting those writes with transactions. A transaction groups statements so they all succeed or none do, following ACID properties. Isolation levels control what concurrent sessions can see, and getting this right prevents lost updates and corrupted records.
Stage: Advanced Querying · Part of the SQL roadmap · Last reviewed 19 November 2026
What to learn in Changing Data
- Insert rows singly, in bulk and from a SELECT query
- Update or delete only the intended rows by checking the WHERE clause first
- Wrap related statements in BEGIN, COMMIT and ROLLBACK
- Describe the four ACID properties with a bank transfer example
- Explain how isolation levels relate to dirty and non-repeatable reads
Changing Data interview questions
What does ACID stand for?
Atomicity means a transaction is all or nothing. Consistency means it moves the database from one valid state to another, respecting constraints. Isolation means concurrent transactions do not interfere improperly. Durability means committed changes survive a crash, usually through a write-ahead log.
What happens if you run UPDATE without a WHERE clause?
Every row in the table is updated, which is rarely intended. Safe habits include writing a SELECT with the same WHERE first, running changes inside a transaction so you can roll back, and checking the affected row count before committing.
Where Changing Data fits in the SQL roadmap
Changing Data belongs to the Advanced Querying stage (beginner level), which takes about 18 hours. Express complex logic.