[Solved] Why might a DELETE trigger cause performance issues in a high-traffic database? — Ans: Because it runs for every deleted row, adding overhead to each delete operation | SQL

SQL - Triggers

Why might a DELETE trigger cause performance issues in a high-traffic database?

ABecause triggers prevent indexes from being used

BBecause DELETE triggers run asynchronously and delay commits

CBecause it runs for every deleted row, adding overhead to each delete operation

DBecause DELETE triggers lock the entire database

Step-by-Step Solution

Solution:

Step 1: Understand trigger execution frequency
DELETE triggers execute for each deleted row, adding processing time.
Step 2: Impact on performance
High volume deletes cause many trigger executions, increasing overhead.
Final Answer:
Because it runs for every deleted row, adding overhead to each delete operation -> Option C
Quick Check:
Per-row triggers add overhead, affecting performance [OK]

Quick Trick: Per-row DELETE triggers add overhead on each deletion [OK]

Common Mistakes:

Master "Triggers" in SQL

9 interactive learning modes - each teaches the same concept differently

More SQL Quizzes

Why might a DELETE trigger cause performance issues in a high-traffic database?