In SQL Server recovery models, which model is commonly described as having “no logging,” even though SQL Server always writes to the transaction log internally? Select the closest correct choice based on standard terminology.

Introduction / Context:
Many study guides casually state that one recovery model does “no logging,” which is misleading. This question checks both conceptual understanding and precise terminology.

Given Data / Assumptions:

• Recovery models: FULL, BULK_LOGGED, SIMPLE.
• We seek the model popularly (but imprecisely) said to do “no logging.”
• Important nuance: SQL Server always uses the transaction log.

Concept / Approach:

In SIMPLE recovery, the log is automatically truncated after each checkpoint and you cannot take transaction log backups. Although logging still happens, you cannot perform point-in-time recovery because the log backup chain does not exist. Textbooks sometimes summarize this as “no logging,” which refers to the inability to back up and replay the log, not the absence of log records.

Step-by-Step Solution:

Verification / Alternative check:

Attempting BACKUP LOG in SIMPLE returns an error. DMVs show log records still exist during activity.

Why Other Options Are Wrong:

Full: fully logged. Bulk-logged: minimal logging only for specific operations; still relies on the log. Differential: a backup type, not a model.

Common Pitfalls:

Believing SIMPLE truly disables the log; it does not. Assuming BULK_LOGGED means “no logging” for everything; only certain bulk operations are minimally logged.

Final Answer:

Simple recovery