Check

diskpart

diskpart

list volume

Assign Drive Letters

diskpart

diskpart

list volume

select volume 3

assign letter=Z

Powershell

Get-Disk

Get-Partition -DiskNumber 1 | Set-Partition -NewDriveLetter Z

SQL Server

An example drive layout for a typical SQL Server implementation...

• C: - Operating System

  • minimum is 40 GB, more if additional software is required

  • normal virtual disks

• D: - Admin drive

  • about 10GB

  • normal virtual disks

• E: - MS SQL data files

  • dependent on number of databases and estimated growth, usually starts from 50 GB

  • RDM disk - individual LUN for partition from SAN, drive partition with an offset of 1024K, 64KB bytes per cluster as the SQL Server allocation unit is 8 x 8KB pages.

• F: - MS SQL transaction log files

  • dependent on number of databases, usually about 30-40% of space used for E:

  • RDM disk - individual LUN for partition from SAN, drive partition with an offset of 1024K, 64KB bytes per cluster as the SQL Server allocation unit is 8 x 8KB pages.

• T: - MS SQL tempdb

  • dependent on estimated system activity, usually start from 20-30 GB, can be skipped on test instance

  • RDM disk - individual LUN for partition from SAN, drive partition with an offset of 1024K, 64KB bytes per cluster as the SQL Server allocation unit is 8 x 8KB pages.

• G: - MS SQL backups

  • dependent of number of databases and estimated growth, usually about 2 x space used for E: but may be 1 x E: if MS SQL allows backup compression

• • RDM disk - individual LUN for partition from SAN, drive partition with an offset of 1024K

Bibliography