DaveWentzel.com            All Things Data

Solid State Drives

A few things I've discovered while researching SSD's.  

  • There are issues with SSD's and their life expectancy.  Particularly, they have a finite number of writes they can handle.  Granted, it's likely you'll never hit that threshold, but it's worth researching.  The drives aren't totally useless when that happens, but they apparently go into a "read only" type of mode.  
  • The drivers use *lots* of RAM.  It's not uncommon to use 1GB+.  
  • You cannot boot from an SSD.
  • It doesn't look like there are RAID controllers available (yet) for SSDs.  That leaves you with software RAID.  
  • You should never need to defrag a volume on an SSD.  SQL Server reorg/rebuilds would still be a good idea from a logical read perspective.  
  • They are extremely expensive, but the IO characteristics make this compelling if you really have an IO bottleneck.  
  • I can't find anything regarding whether or not database compression would be a good idea on an SSD.  

So what data would you put on an SSD?  

  • If money is no cost, everything.
  • Otherwise, if you have tempdb contention, start there.
  • Then consider moving your database or a filegroup with your most IO-intensive data objects.  


SAN Home