An administrator is concerned about a volume on a server containing SQL databases with only 3% available disk space. The administrator is considering turning on NTFS compression to create space…

Question

Options

• ACompressing volumes that contain databases is highly recommended due to the poor space
• BCompressing a volume using NTFS is also known as compacting
• CCompressing a volume containing databases is not recommended since it slows down the speed
• DAdding additional memory is a better solution to a space problem since databases are stored in

• A
  3% (1)
• B
  3% (1)
• C
  84% (27)
• D
  9% (3)

Explanation

NTFS compression is a filesystem-level feature that transparently compresses and decompresses data on read/write. While it frees up disk space, it introduces significant CPU overhead for every I/O operation. Database engines like SQL Server perform extremely high volumes of random read/write operations, and the constant compression/decompression cycle creates a severe performance bottleneck. Microsoft and most database vendors explicitly advise against enabling NTFS compression on database volumes. The correct remediation for a full database disk is to add more physical storage, archive old data, or expand the volume - not compress it. Option A is incorrect because compression is discouraged, not recommended. Option B is incorrect because NTFS compression and compacting (defragmentation/shrinking) are distinct operations. Option D is a distractor - memory does not solve a disk space problem.

No community discussion yet for this question.