A database analyst notices a query statement is running slowly. Which of the following should the analyst review first?

Question

Options

• AMissing indexes
• BCode
• CTable integrity
• DDatabase patches

• A
  77% (24)
• B
  6% (2)
• C
  13% (4)
• D
  3% (1)

Explanation

Missing indexes (A) are the first thing to check for slow queries because an index allows the database engine to locate rows without scanning the entire table - their absence is the single most common and impactful cause of poor query performance, and identifying one is quick with an execution plan.

Why the others are wrong:

• B (Code): Reviewing application code is a broader, more time-consuming process and is secondary to diagnosing the database execution plan first.
• C (Table integrity): Integrity issues (corruption, constraint violations) cause errors or wrong data, not typically slow performance.
• D (Database patches): Patches address bugs or security vulnerabilities; a missing patch rarely explains a specific slow query in isolation.

Memory tip: Think "Index First, Fix Fast" - when a query is slow, indexes are the fastest win to check and resolve before diving into code or infrastructure.

No community discussion yet for this question.