Topic: What it is better to throw on SSD?
In what an essence, we want to buy SSD for one not so important server, the budget is restricted, now there all on the normal disks, three spot-checks 1 and one 10 spot-check. And so if to look io_virtual_stats on reading the most loaded basis at it tempdb, write stall at all 4 files (they lie together) in 3 three times above than at DB_One (we name it so), but Read in time 10 it is less than at DB_One, at which Read_stall the biggest. DB_One lies separately from tempdb, but together with DB_Two which on loading it is approximately equal DB_One.
spot-check 1.1 - system, spot-check 1.2 tepmdb with a heap of remaining small bases, spot-check 1.3 Broad gulls of all bases, spot-check 10 DB_One and DB_Two, data files. It is necessary to disassemble somehow this dump, and here we with colleagues had a dispute:
1) I suggest to buy one SSD on 512 (in tempdb it is much written to time of different loadings happens to 200-400 grows) if it departs anything terrible, them a stop to working hours for 10-20 minutes. After transfer DB_One to transfer on spot-check 1.2 where was tempd. DB_Two weighs much and it not to transfer.
2) Colleagues offer to buy two SDD on 256, to make 1 spot-check, to thrust there DB_One and anything else not to touch.
3) Suggest to buy simply (not a variant certainly).
I will add that 50 heaviest requests in respect of IO if to look under plans, in the majority in temporary tables and update temporary tables.