SQL Server - Separating data, log, and TempDB files on a SAN I have a SQL Server connected to a SAN. Our new storage vendor recommends that all LUNs span the entire disk array, which is RAID5. I would normally request 3 separate LUNs (data, log, and TempDB) from the SAN administrator, but given the new vendor's recommendation, is there any point in creating separate LUNs? Or would I see the same performance if everything was in one LUN since it would span all disks anyway?

Great article here, but doesn't quite address my exact situation:
http://www.brentozar.com/archive/2008/08/sql-server-on-a-san-dedicated-or-shared-drives/
One thing to consider is that the log files are sequential writes where as the data files are non sequential.  That is one of the reasons for separate LUNs.  Log files write faster if they are on their own LUN because the spindles don't have to skip around, just write sequential.  If you add in a data file then the spindles have to skip around and you lose some performance.  I'm hoping I got the right terminology there as I'm not all that familiar with SANs themselves.  The idea behind it should be however.

Frequently vendor recommendations are wrong when it comes to SQL Server.  Just because SQL Server has different needs than most applications that use a SAN.