What Is Database Testing?

Database testing is the process of validating data stored in backend databases to ensure accuracy, integrity, consistency, security, and performance. In manual database testing, testers use SQL queries and logical checks (not automation scripts) to verify that application data is correctly stored, retrieved, updated, and deleted.

Why Database Testing Is Used

• To ensure UI data matches database records
  
• To validate business rules at DB level
  
• To detect data loss, duplication, or corruption
  
• To verify transactions, constraints, and relationships
  

Because backend data issues can break entire systems, manual database testing interview questions are very common in testing roles.

Step 1: Understand Business Rules

• Know how data should be stored
  
• Identify mandatory and optional fields
  

Step 2: Validate Schemas & Tables

• Table names
  
• Column data types
  
• Default values
  

Step 3: Check Constraints

• Primary Key
  
• Foreign Key
  
• NOT NULL
  
• UNIQUE
  

Step 4: CRUD Validation

Operation	SQL Used
Create	INSERT
Read	SELECT
Update	UPDATE
Delete	DELETE

Step 5: Validate Stored Procedures, Triggers & Indexes

• Output correctness
  
• Side-effects (logs, audits)
  
• Performance improvement
  

---

Manual Database Testing Interview Questions (100+ Q&A)

---

Basic Manual Database Testing Interview Questions (1–20)

1. What is manual database testing?

Manual database testing is validating backend data using SQL queries without automation tools.

2. Why is database testing important?

Because incorrect data can cause financial loss, system crashes, or compliance issues.

3. What skills are required for manual DB testing?

• SQL knowledge
  
• Understanding of DB concepts
  
• Business logic awareness
  

4. What are CRUD operations?

• Create – INSERT
  
• Read – SELECT
  
• Update – UPDATE
  
• Delete – DELETE
  

5. What is a primary key?

A column that uniquely identifies each row.

6. What is a foreign key?

A column that references a primary key in another table.

7. What is data integrity?

Ensuring correctness and consistency of data.

8. Difference between DELETE and TRUNCATE?

DELETE	TRUNCATE
Can rollback	Cannot rollback
WHERE allowed	No WHERE
Slower	Faster

9. What is normalization?

Process of reducing redundancy in tables.

10. What is denormalization?

Adding redundancy to improve performance.

---

SQL Interview Questions for Testing (21–45)

21. Write a query to fetch all records.

SELECT * FROM users;

22. Fetch users with age > 30.

SELECT * FROM users WHERE age > 30;

23. Difference between WHERE and HAVING?

WHERE	HAVING
Filters rows	Filters grouped data
Used before GROUP BY	Used after GROUP BY

24. GROUP BY example

SELECT department, COUNT(*)

FROM employee

GROUP BY department;

25. HAVING example

SELECT department, COUNT(*)

FROM employee

GROUP BY department

HAVING COUNT(*) > 5;

26. What is DISTINCT?

Removes duplicate values.

SELECT DISTINCT city FROM customers;

27. What is ORDER BY?

Sorts query results.

SELECT * FROM users ORDER BY created_date DESC;

---

JOIN-Based Database Testing Interview Questions (46–65)

46. What is a JOIN?

Used to combine data from multiple tables.

47. Types of JOINs?

• INNER JOIN
  
• LEFT JOIN
  
• RIGHT JOIN
  
• FULL JOIN
  

48. INNER JOIN example

SELECT o.order_id, c.name

FROM orders o

INNER JOIN customers c

ON o.customer_id = c.id;

49. LEFT JOIN use case?

To find records without matching entries.

SELECT c.name, o.order_id

FROM customers c

LEFT JOIN orders o

ON c.id = o.customer_id;

50. Scenario: Find customers with no orders

SELECT c.id

FROM customers c

LEFT JOIN orders o

ON c.id = o.customer_id

WHERE o.id IS NULL;

51. What is self join?

Joining a table with itself.

---

Indexes, Stored Procedures & Triggers (66–85)

66. What is an index?

Improves query performance by reducing scan time.

67. Types of indexes?

• Clustered
  
• Non-clustered
  
• Composite
  

68. How to validate index usage?

Using EXPLAIN or execution plans.

69. What is a stored procedure?

Pre-compiled SQL code stored in DB.

70. Stored procedure example

CREATE PROCEDURE getUser(IN uid INT)

BEGIN

  SELECT * FROM users WHERE id = uid;

END;

71. How do testers test stored procedures?

• Input validation
  
• Output verification
  
• Error handling
  

72. What is a trigger?

Automatically executed SQL on data changes.

73. Trigger example

CREATE TRIGGER audit_update

AFTER UPDATE ON orders

FOR EACH ROW

INSERT INTO audit_log VALUES (NEW.id, NOW());

74. How to validate triggers?

• Perform INSERT/UPDATE
  
• Verify audit/log table
  

---

Scenario Based Database Testing Questions (86–105)

86. Scenario: Validate user registration

• Check user table entry
  
• Validate default values
  
• Verify password encryption
  

SELECT * FROM users WHERE email=’test@gmail.com’;

87. Scenario: Validate soft delete

SELECT * FROM users WHERE is_active=’N’;

88. Scenario: Duplicate email issue

SELECT email, COUNT(*)

FROM users

GROUP BY email

HAVING COUNT(*) > 1;

89. Scenario: Validate transaction rollback

• Force failure
  
• Ensure no partial data saved
  

90. Scenario: Update operation validation

SELECT balance FROM accounts WHERE acc_id=101;

---

Advanced Manual Database Testing Interview Questions (106–125)

106. What is a transaction?

Group of SQL statements executed as one unit.

107. ACID properties?

• Atomicity
  
• Consistency
  
• Isolation
  
• Durability
  

108. What is a deadlock?

Two transactions waiting for each other.

109. What is isolation level?

Controls visibility of data changes.

110. What is data migration testing?

Validating data after moving between systems.

---

Real-Time Use Cases

🏦 Banking

• Transaction consistency
  
• Balance calculations
  
• Audit logs validation
  

🏥 Healthcare

• Patient history accuracy
  
• Record immutability
  
• Access control validation
  

🛒 E-commerce

• Order vs payment validation
  
• Inventory updates
  
• Refund reconciliation
  

---

Common Mistakes Testers Make

• Skipping negative scenarios
  
• Ignoring NULL checks
  
• Not validating rollback
  
• Testing only UI data
  
• Missing performance validation
  

---

Quick Revision Sheet

✔ SELECT, WHERE, JOIN
✔ GROUP BY, HAVING
✔ CRUD operations
✔ Index testing
✔ Stored procedures
✔ Triggers
✔ Transactions

---

FAQs – Manual Database Testing Interview Questions

Q1. Is automation mandatory for database testing?
No, manual SQL testing is often sufficient.

Q2. How much SQL is required?
Strong SELECT, JOIN, GROUP BY knowledge is enough.

Q3. Are scenario-based questions important?
Yes, especially real-time SQL validation interview questions.