July 23, 2009 at 11:57 am
My current databases have very little disk contention and are setup on single or double file groups only. For a new application the software provider has asked for multiple file groups setup across multiple locations. The have asked for 32 separate locations. Each location should use a separate device. Here is the exact verbage:
For optimal performance, do as follows:
•Use the advanced configuration option to specify as many locations as possible on the SQL Server, up to the maximum of 32.
•Use a separate device for each location. If you specify more than one location on the same device there is no performance benefit.
So based on this my understanding is they want separate physical devices, like a C,D,E, etc drive or possibly a mount point inside a drive letter? Is this a correct understanding?
I am not a SAN expert and trying to best plan for this new database. What would be the configuration needs for a SAN? Since you have LUNs and such, do you still have the same needs as individual physical disks? I can create 32 filegroups like they want and put them all on my data drive, but this seems like it would not be optimal. So I am trying to figure out how I should configure the filegroups on the san to achieve the setup they desire.
Also... in general I am looking for what is best practice for file groups on a san? Do people usually use different luns or whatever to present different drive letters, or just place it on one lun since there are many disks?
Thanks for any info...
July 28, 2009 at 9:48 pm
First off I wanted to point out that they aren't asking for 32 seperate locations, they are saying that 32 is the max. Most of us have seperate data, log, and backup spaces. If you have high contention an additional data and/or log space may be added to spread it out.. Not sure if this answers your question..
CEWII
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply