asked on

Volume Mount Points vs Drive Letter assignment in a Oracle/SQL Server DB Environment (Pros/Cons)

We are trying to develop a standard server build for Windows Server 2003. The question is what are the advantages or disadvantages to using Volume mount points for such things as log files etc. Is there and advantage to mount points over assigning drive letters other than the 26 drive letter limitation?

Thanks in advance for you help

ASKER CERTIFIED SOLUTION

cuziyq

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

cuziyq

One thing you might try is the DFS functionality of Windows Server 2003. Store your log files or whatever you're trying to do a the DFS root. It basically appears as a network resource, and the name of that resource will stay the same no matter where that resouce is on the network -- even if it's on the local machine.

michael_faries

ASKER

So what we are looking for is a way to store files on a huge partition (3.5TB) and keep the files seperate but share the space. The problem we are running into is that we create a dir for logs at 5GB or whatever and then that space fills up and we are stuck with a static partition. Creating multiple Volume Mount Points across the large disk array will allow us to keep the file seperate and grow them as needed. Oracle and SQL will be using these various directories.

michael_faries

ASKER

We are trying the mount point solution. Works for our application so far. Thanks for the help and suggestions.

michael_faries

ASKER

Thanks for the input... Awarded points to you for your help even though we went with the Mount Points solution on a trial basis.