In SQL Server recovery planning, under which recovery model are all database changes fully logged, enabling point-in-time recovery using transaction log backups?

Introduction / Context:
Recovery models control logging behavior, log truncation, and restore capabilities. This question asks which model fully logs all changes and supports point-in-time recovery.

Given Data / Assumptions:

• Recovery models considered: FULL, SIMPLE, BULK_LOGGED.
• Requirement: all changes fully logged and restorable to a specific time.
• Log backups are taken regularly.

Concept / Approach:

FULL recovery model logs every change. With a sequence of full/differential plus transaction log backups, you can restore to a particular point in time by replaying log records up to a marked stop time.

Step-by-Step Solution:

Verification / Alternative check:

Test a restore chain with FULL model: full backup → several log backups; restore to a specific time using STOPAT.

Why Other Options Are Wrong:

Differential recovery: not a recovery model. SIMPLE: no log backups, cannot do point-in-time. BULK_LOGGED: may prevent point-in-time during bulk operations.

Common Pitfalls:

Thinking “simple = no logging”; SQL Server always logs, but SIMPLE truncates log and disallows log backups. Mislabeling “differential” as a model (it is a backup type).

Final Answer:

Full recovery