When does one consider moving a database to a SAN/NAS environment? Are there any "best practices" for how large the database should be where a SAN/NAS would be most suitable? What would the recommended size be for a SQL/Oracle database if it were moved into a SAN/NAS?
You've asked the toughest question for NAS. You need to know what your performance requirements are first. In general, the rule of thumb has been if you have a performance requirement for your online transaction processing (OLTP) application you don't use NAS because of the overhead in the TCP/IP implementation and with the variables in Ethernet networking. Improvements have been made with DAFS (direct access file system) that provides outstanding performance and with TCP/IP accelerators.
Both these require different NICs (network interface controllers) and driver software. Size does have something to do with it but I think you may not even get to the size question if you make the decision about basic performance. SAN should be no different in the decision making for direct attached storage regarding performance and size.
Evaluator Group, Inc.
Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .bphAaR2qhqA^0@/searchstorage>discussion forums.
Dig Deeper on Data storage strategy
In case you've missed anything, here's a roundup of some of the best original technical content that appeared on SearchStorage.com the week of April 19-23. Tips and Ask the Expert Q&A's cover DR, compliance and replication buying tips.
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.