Sql-server – Recommendations for SSD for server and database use

You should always limit the amount of RAM that SQL Server can use, otherwise the SQL Server won't leave any RAM for the OS.

You'll usually want to leave 1-2 Gigs of RAM for the OS and the other software on the machine.

The Intel drives are known to have write caching that violates PostgreSQL (and other database) expectations; see Reliability section of the documentation for details on what those are. They don't flush their write cache out when the OS executes a normal fsync call, which is normal for SATA drives. And this will result in database corruption if the server crashes due to a power interruption. The only real option is to therefore turn the write cache off completely, and if you do that you'll discover the performance is terrible; the expected longevity of the drive plummets too. Some have reported even then it doesn't work right. See SSD, XFS, LVM, fsync, write cache, barrier and lost transactions for more information.

The recently released OCZ Vertex 2 Pro drives using a Sandforce controller and having an Ultracap battery backup are the first relatively inexpensive SSD model to reach the market worth considering here. That's passed all of the reliability tests those of us on the PostgreSQL Performance mailing list have come up for stressing this type of device, the Intel drives failed miserably. See Testing Sandforce SSD for benchmarks and reliability test information. There are some much more expensive "enterprise" SSDs that work fine as well, but those are all multi-thousand dollar devices. Note that you must be careful to get the Vertex 2 Pro, the cheaper Vertex models will not have the required Ultracap that makes this all work.