How manage drive letter limitation for windows server 2012 R2

71957367 21 Reputation points
2021-12-21T08:15:41.047+00:00

Dear All

I would like your support, in my environment have windows server 2012 R2 run for SQL Server 2016, our DBA is require many disk and drive on these server to separate between database file and Log file, from now it have 10 Drive letter ( C,D,E,F,G,H,I,J,M,N ), and they require more 8 Drive letter, I am not sure it have some limitation on windows server or SQL or not? and it have effect to SQL performance or not ?,

if you have some idea or reference, please share to me

Windows for business | Windows Server | User experience | Other
SQL Server | Other
{count} votes

5 answers

Sort by: Most helpful
  1. Dan Guzman 9,406 Reputation points
    2021-12-21T12:10:19.103+00:00

    Different drive letters will work without performance concerns. An alternative (only necessary once you exhaust drive letters) are mount points. To create a mount point, create an empty folder on any existing NTFS volume and then use the Disk Management mmc to mount the disk volume in that empty folder instead of assigning a drive letter. Repeat for each drive. See mount a drive in a folder for detailed instructions.

    Below is an example of what the directory structure might look with all mount points on drive M: folders.

    M:\MountPoint_Disk1
    M:\MountPoint_Disk2
    M:\MountPoint_Disk3
    M:\MountPoint_Disk4
    ...
    
    1 person found this answer helpful.
    0 comments No comments

  2. Olaf Helper 47,516 Reputation points
    2021-12-21T08:33:16.617+00:00

    The limitation is on Windows Server side, you can have drive letters from A till Z, so 26.

    The requirements by your DBA is a bit strange for me, I never saw a SQL Server installation with more the lets say 9 disks.

    0 comments No comments

  3. AmeliaGu-MSFT 14,006 Reputation points Microsoft External Staff
    2021-12-22T02:39:38.23+00:00

    Hi 71957367,

    Agree with others.
    In addition, you can use Performance Monitor to check if there are any disk I/O performance issues. Please refer to Slow I/O - SQL Server and disk I/O performance and SQL Server monitoring tools for disk I/O performance which might be helpful.

    Best Regards,
    Amelia


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. Docs 16,226 Reputation points
    2021-12-27T07:27:23.64+00:00

    For management of multiple drive letters consider using these third party software:

    https://www.nirsoft.net/utils/drive_letter_view.html

    https://www.nirsoft.net/utils/usb_devices_view.html

    .
    .
    .
    .
    .

    On the left side of each post there is /\ with a number: click = a helpful post

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    .
    .
    .
    .
    .

    0 comments No comments

  5. Tom Phillips 17,771 Reputation points
    2021-12-27T18:22:30.06+00:00

    Just to add.

    On modern SAN technology, having multiple separate drive letters for data files is not really needed. Before doing any partitioning or mapping of drives, you should consult your SAN provider for instructions for best using SQL Server on their solution.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.