Answer by Matt Whitfield ·
Just to spell out my 2 cents in a separate answer:
Hope that helps.
If you have money to burn, you might want to check out RamSAN systems. They're pretty awesome. Actually, I had one in to test once, and it was pretty good on the whole IO front both in terms of rate and IOPS, but it didn't make our application much faster in practice because it was pretty well optimised, and most of the time taken was network latency anyway.
Answer by Fatherjack ·
It depends what connects you to the SAN and how the local disks are configured. If you have the time then benchmark both and pick the one that will best suit your needs. There are so many different factors that impact on your situation it will be impossible to answer it here, based on the information you have provided. I would recommend reading up on your options in Books Online and some blogs of SQL Server performance tuning gurus like Brent Ozar
Answer by Grant Fritchey ·
The reasons to use a SAN are not, strictly speaking, technical. We use a SAN because it provides a mechanism for rock solid high availability. In terms of shear performance, there are faster methods to store data. But few are as reliable. We use the SAN because it gives the business the warm & fuzzies it needs to know that it's data will always be available. Funny thing is, the vast majority of data on the SAN is unstructured data, not relational data.
Answer by TimothyAWiseman ·
As many others have mentioned, there are a lot of variables floating around in your choice of storage. I am not going to rehash all the good points made by Matt and Grant and others, but I think two are worth reemphasizing/rephrasing.
You will generally get better performance from the same harddrive attached directly to the machine then you will from a San.
You will generally have more flexibility in the San. You can often more easily add storage space to a San without downtime than you can with direct storage. Also, you can generally do virtual reallocation of the space that is already there from one server or designated drive to another easily.
You may notice that I and many of the other posters are using a lot of caveats like generally and often. That of course is because a lot depends on the specific configurations and pieces of hardware that you are looking at and your use case. Fatherjack expressed this very well.
One of the big points Grant correctly made was that Sans are generally more reliable. Of course he is right, but remember that you can install a well configured RAID setup with automatic backup to another media all into one (large) computer box without problems and have enormous reliability on the storage side of things, and on the flip side, a poorly configured San with no redundancy could be unreliable.
If you really want to boil it down to a rule of thumb, if you have a very small number of servers (say 3 or fewer) then you are probably better using local drives. They will generally be faster and cheaper and if configured properly can be quite reliable. If you have numerous servers and do not have a need for physical separation of data (this is often required with some types of sensitive data), then you are better off with a San. The maintence tends to be easier and benefits such as greater flexibility and ability to set up failover clustering can be valuable.
Answer by Blackhawk-17 ·
It really isn't black & white.
SANs have tools for cloning, data backups etc.
SANs are typically supported by storage specialists so another group is caring for the physical aspect.
SANs are probably easier, from the O/S and SQL Server point of view, when it comes to adding space and/or spindles.
SANs are used for MSCS.
Local drives are easier to configure.
The entire server can be moved to a new location with relative ease if the drives are local.
Fewer support groups required to manage the system when local drives are used.
Basically it comes down to choosing what you need. As Fatherjack said benchmark the differences if you can and then weigh the differences.
Answer by DaniSQL ·
Local disks are way cheap than SAN, but SAN gives you flexibility and Scalablity.
Check this page out. It has the right questions to ask before you decide. Like how many days of backup you want to store in disks? What kind of RAID do you want to use for Data, Log, Backup, tempdb? Also do you want to place these files in their own drives? etc..
Also if you are using SAN keep in mind you can make snapshot copy of your data etc.
Regarding performance of DAS Vs SAN check out an article by Linchi Shea (Which is Faster: SAN or Directly-Attached Storage?).