nerdexam
CompTIA

SG0-001 · Question #144

For provisioning SAN volumes to high performance OLTP databases, which of the following describes a best practice?

The correct answer is A. Volumes for the redo logs should be created from different disks than the data volumes.. A best practice for provisioning SAN volumes to high-performance OLTP databases is to separate redo logs from data volumes onto different physical disks to prevent I/O contention.

Storage Implementation

Question

For provisioning SAN volumes to high performance OLTP databases, which of the following describes a best practice?

Options

  • AVolumes for the redo logs should be created from different disks than the data volumes.
  • BVolumes for each database should be provisioned on separate fabrics.
  • CVolumes for indexes, redo, and archive logs should be on separate storage arrays from the
  • DVolumes for the redo logs from each database should be created from the same disks.

How the community answered

(29 responses)
  • A
    83% (24)
  • B
    3% (1)
  • C
    3% (1)
  • D
    10% (3)

Why each option

A best practice for provisioning SAN volumes to high-performance OLTP databases is to separate redo logs from data volumes onto different physical disks to prevent I/O contention.

AVolumes for the redo logs should be created from different disks than the data volumes.Correct

Separating redo log volumes from data volumes onto different physical disks (or RAID groups/LUNs backed by different spindles) is a critical best practice for OLTP databases to prevent I/O contention, as redo logs have highly sequential write patterns while data volumes often have more random I/O.

BVolumes for each database should be provisioned on separate fabrics.

Provisioning volumes for each database on separate fabrics is primarily for high availability and redundancy, not specifically for optimizing I/O performance of different database components like redo logs versus data.

CVolumes for indexes, redo, and archive logs should be on separate storage arrays from the

While separating indexes, redo, and archive logs onto different storage arrays can provide maximum isolation and performance, it is a very expensive and often unnecessary practice for all but the most extreme performance requirements; separating onto different disks (as in option A) is a more common and effective best practice.

DVolumes for the redo logs from each database should be created from the same disks.

Creating redo logs from each database on the same disks as other redo logs or even data volumes would exacerbate I/O contention, which is contrary to best practices for high-performance databases.

Concept tested: SAN volume provisioning for OLTP databases

Source: https://learn.microsoft.com/en-us/sql/relational-databases/performance/optimize-tempdb-performance-in-sql-server?view=sql-server-ver16#best-practices-to-optimize-tempdb-performance

Topics

#SAN provisioning#OLTP databases#Performance optimization#Disk layout

Community Discussion

No community discussion yet for this question.

Full SG0-001 Practice