|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 5:45 AM
Points: 462,
Visits: 643
|
|
I'm not quite sure where is the best place to post this question but here goes.
My understanding is that if I were to install Windows onto an SSD drive then I would no longer want to defrag the hard disk - I was wondering if I were to start using flash storage arrays of one sort or another (I don't have a variety in mind, just a question out of interest) would index fragmentation still be an issue and need dealing with - presumably it would become an issue eventually but the rewriting activity would need to be minimised?
Does anyone know of any studies into this sort of thing with SQL Server & SSDs?
Thanks
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 9:55 PM
Points: 6,720,
Visits: 11,759
|
|
Brent Ozar and Paul Randal both have posted research and findings on the topic. Google or Bing are your friend there. I just pulled back a bunch of relevant results.
__________________________________________________________________________________________________ There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Believe you can and you're halfway there. --Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 3:30 AM
Points: 37,725,
Visits: 29,982
|
|
Fragmentation, probably not. Low page density (a side effect of fragmentation), hell yes. Having half of your expensive SSD going to waste because of low page density isn't the greatest of ideas.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 5:45 AM
Points: 462,
Visits: 643
|
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Yesterday @ 6:54 PM
Points: 3,578,
Visits: 5,120
|
|
GilaMonster (2/15/2013) Fragmentation, probably not. Low page density (a side effect of fragmentation), hell yes. Having half of your expensive SSD going to waste because of low page density isn't the greatest of ideas.
I agree. I think Jonathan Kehayias did a blog post about that (and also about sequential IO actually being faster on SSDs too, just like on rotating media).
Best,
Kevin G. Boles SQL Server Consultant SQL MVP 2007-2012 TheSQLGuru at GMail
|
|
|
|
|
Say Hey Kid
      
Group: General Forum Members
Last Login: Monday, May 20, 2013 12:28 PM
Points: 675,
Visits: 2,031
|
|
Yes, SSD's (and SSD's in RAID configurations) are indeed still faster for sequential access than they are for random access (significantly, in the case of writes, slightly in the case of reads). Spinning disks are significantly faster in sequential access for both writes and reads.
Note that I've provided some SSD performance results in the RAID and Its impact on your SQL performance thread.
Testing techniques and how to load the output into SQL Server comes from the FusionIO thread.
|
|
|
|