Spanned Volume - benefits???
-
Hello,
Our development SQL 2005 database has data files on a spanned volume - I understand that means what is one drive letter on the server is really multiple seperate SAN disks on the SAN.
Questions -
[font="Tahoma"]1. Is there any benefit to SQL out of this spanned volume layout? parallel writes/reads due to more spindles being available????
2. Does SQL even recognize the multiple disk configuration to leverage this for better performance?
3. When I check perfmon for these individual disks, I see data being written only to 3:F and 6:F continuously, and only INTERMITTENTLY to 2:F. There is nothing being written to 4:F and 5:F, and that written to 2:f is not in the same proportion as 3 and 6. Why would that be?[/font]
I understood the spanned volume better when I looked the Computer Management Console/Disk Management -
AS ALWAYS, ANY GUIDANCE YOU COULD PROVIDE IS TRULY APPRECIATED!!!
-
personally I dont like spanned volumes. AFAIK it offers no extra IO or resilience. The only reason we landed up with spanned volumes on a few servers was because we had a massive datafile (4TB) that wouldn't fit on a single partition. So, spanned volumes may be unavaoidable in some some cases but I would prefer to have more drive letters on unspanned volumes instead of fewer drive letters but bigger volumes.
my 2c
thanks
SQL_EXPAT
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply