|
Dear Colleagues In the company that I work we need to buy a server .So they asked me what are the best specifications for SAN(Storage area network):
and I will give you the idea that what we want to do AS the DBA they asked me the best practice for SAN? I need the good reference to put the specification for the server ,what is the best server? any Idea How to do that ? HP DL380G7 X5660 Six Core High Performance Rack Server (583970-421) –Processor(s): (2) Intel® Xeon® Processor X5660 (2.80 GHz,12MB L3 Cache, 95W, DDR3-1333, HT, Turbo 2/2/2/2/3/3) many thanks
(comments are locked)
|
|
It depends.
Thank you for quick respond .
What's your data set size? as I I mentioned below for 20 computer scan and send to sql server , the other 500 computer I don't now What are your I/O requirements? could you plz tell me what you mean.
Jul 05 '12 at 09:58 AM
MuhSQL
By IO requirements, I mean:
These two figures may provide more information about the storage requirement - for example, a system with a very high data throughput with low latency would need to be serviced either by a very large number of physical disks in a RAID configuration, or could be handled by just a couple of SSDs...
Jul 05 '12 at 11:26 AM
ThomasRushton ♦
Thanks a lot Thomas for your great notes and Anuj "SQL Server Hardware Choices Made Easy" Really it's very good book thank you Now Thomas asked me a question "What are your I/O requirements?" Is this query good to answer the question Now , let say we did it to simple database like AdventureWorks abd the result was
how will be useful for us ? I hope I answer one of your Question Thomas .
Jul 06 '12 at 10:03 AM
MuhSQL
(comments are locked)
|
|
There is a lot of information missing here, that you seem not to know yourself rather than not supplying it in your question. I suggest finding out what data access patterns are going to be. You cannot size a system for 520 users and only know what 20 of those users are going to be doing. Be that as it may, a general rule of thumb for SQL Server that I follow is to prioritize your hardware spending as follows:
The SAN portion is the most difficult and if you have no experience, then get in touch with an expert (in your company maybe). Brent Ozar has a pretty good Best Practice for SAN Storage article that may help here. I strongly suggest you get more details about the applications that are going to be working with the SQL Server and if possible get some sort of baseline for the application. @WilliamD +1. @MuhSQL Now a days with virtualization so common, general trend is to get one big machine instead of 2/3 mediocre machines. But it all depend upon the usage patterns, workload etc. The point is to keep bigger picture in mind which can save you licensing costs, physical maintenance etc. Also, the most common hurdle in such situations could be the company's budget. You may want to buy a bigger machine but may end up with a mediocre one ;)
Jul 05 '12 at 11:07 AM
Usman Butt
(comments are locked)
|
|
Thought to share free ebook from Glenn Berry's new "SQL Server Hardware Choices Made Easy" has plenty of tips for choosing right hardware for your SQL Server.
(comments are locked)
|


