Quick off topic - Hey, sir-astral. If you look back at my post (121), you'll see I was commenting on someone else's post. You chime in, tell me my article from 6/18/2009 (this month, 11 days ago) is too old. I provide you with a compliment (post 123) and ask a question (because I'm curious if there's a clear answer or good article out there)... you respond (post 124) by telling me you already made some posts and saying "I sit in a room chating and arguing with Professionals that have more certifications than you have letters in your name." I chime back in in post (125), indicating that I did not doubt your tech know-how based on past posts, but instead doubted your reading comprehension (as I quoted the actual compliment I paid you). Then, Jafo, an SD Staffer that I have never chatted with before (post 128), takes a shot at you for the high brow "I sit in a room chating and arguing with Professionals that have more certifications than you have letters in your name." This pisses you off... and you lash back. Anyway, final recap - I don't claim to know more than you. I work for a fortune 1000 company as a SQL developer and run a custom computer business on the side... because its my hobby. I research new technology as I get ready to buy/build new desktop PCs, and I'll probably be building a new rig for myself in a month or so. So, I'm very interested in this topic, especially if SSD is good for desktops now AND can outperform for the the current price point vs current HDs. That's all. So, please don't take any offense. None meant, and I'm sure you have valuable comments to add to the thread. As it stands, I'm going to read the whole thing to see what I missed and see if I can add something constructive as well. Cheers.
End of pacov's quote
Yes I did notice at the time that you were responding to someone else. Which is why I only said that the articles were old. It was not meant to insult, it was only meant to be informative, so please accept my apologies if you feel they are in order.
Now, I am glad you mentioned your SQL background. I do not develop for SQL but I do manage database backup, security, and light maintenance. Right now I can say you know more than me about SQL for the most part, but I will assure you that SSD would knock your socks off if you utilized an SSD to contain your database. Unless you are doing something special you will be running your SQL in OLTP mode and not OLAP. The links I posted regarding OLTP database performance a single SSD showed absolutely stellar performance vs HDD.
Now as you know SQL devs really like to have as much RAM as possible so you can cache as much of the SQL database as possible and improve performance. But we already know that often times a single SQL server will house many databases, and just 1 database is already larger than system RAM. So when a large complex SQL query is run, you can imediately see performance start to fall because the disk subsystem is being taxed. Now since any OLTP type database rely's on DISK more than any other system resource you can see why SSD completely rules that scene.
Now, I will tell you about an experience at my company regarding an Enertia database that is about 70gigs in size. About once a month a massive financial report is run with several millions of dollars and several thousand checks. This process takes about 3 hours for the SQL server to complete, with another 2.5 hours for the client to parse all the results of the query.
SQL server is a Win2k3 R2 Quad Xeon 2.8Ghz, 8 Gig RAM, and 6x 15k SAS drives in RAID5. These drives are optimize for random IO and benchmarks around 2.7 to 3.1 MS in latency.
The client processing the data is a workstation with 8 gigs of RAM and running Win 2k3 R2 and is a Dual Core Xeon at 2.6Ghz. A pair of 10k SAS in RAID1 (mirror)
A couple of things to keep in mind. The SQL server is also serving 5 other production databases during this entire run.
We installed a single SSD on the server as a test, and fired up a Virtual machine on another SSD and gave it only 1 gig of RAM.
We ran this very same 5+ hour report on the SSD's and some jaws dropped. The SQL Server roasted the query and completed it in just over 25 minutes, and the Client processed the data in about 20 minutes.
SSD's reduced the time to run this report by unbelievalbe amounts. 5 hours down to 1. That's quite a performance increase, just by upgrading the disk subsystem.
The idea that RAM will be a better performance upgrade vs SSD has already been proven incorrect. As you can tell, not only do I have article links to backup my claims I also speak directly from experience.
In case you missed the link in one of my past posts here is the link to the article regarding SQL servers and SSD.
http://it.anandtech.com/IT/showdoc.aspx?i=3532&p=1