SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


All Flash


All Flash

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)SSC Guru (151K reputation)

Group: Administrators
Points: 151536 Visits: 19455
Comments posted to this topic are about the item All Flash

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
call.copse
call.copse
SSCertifiable
SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)

Group: General Forum Members
Points: 5710 Visits: 2015
Nice idea (the tempdb thing) - I can think of one inherited application this could easily buy some time with. I'll investigate, cheers.
cdonlan 18448
cdonlan 18448
SSC-Enthusiastic
SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)

Group: General Forum Members
Points: 103 Visits: 283
TempDB was where we first experimented with SSD's on our accounting system and it made a huge difference by greatly improving the I/O latency (we have a lot of EDI feeds into it). While I'd be first to say "write better code" it's usually not an option with most vendor's software so you opt for throwing more or better hardware at it, be it RAM or SSD's or some kind of indexing strategy. We will be spending a lot on SSD's this year where they will be dedicated to critical DBMS servers on our SAN, because like you said it can be a very cost effective tool.
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (69K reputation)SSC Guru (69K reputation)SSC Guru (69K reputation)SSC Guru (69K reputation)SSC Guru (69K reputation)SSC Guru (69K reputation)SSC Guru (69K reputation)SSC Guru (69K reputation)

Group: General Forum Members
Points: 69017 Visits: 18570
I think the tempdb suggestion is an excellent idea. It could be a very good investment.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Miles Neale
Miles Neale
SSCarpal Tunnel
SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)

Group: General Forum Members
Points: 4300 Visits: 1695
Will our code skills get better?

Over the years I have seen people come onboard who are really good and getting better. They stay a while and are gone. If you are lucky you can keep them a few years. Then you start over again. New person, new skill set, same learning curve, same complex business practices. Once they achieve mastery, they again are gone and you cycle again and again. All the time you are using their product which might not be getting better at all.

So if some are going to get the increase in speed or what we use to call throughput you might only get it by advancing the technology. The idea of throwing more hardware at a solution has not always been the best idea, but some have no option. TO this this is a great idea.

Not all gray hairs are Dinosaurs!
TravisDBA
TravisDBA
Hall of Fame
Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)

Group: General Forum Members
Points: 3380 Visits: 3069
Just remember three main things about SSD's before you run off and start putting stuff on them:

1. SSDs tend to wear out. The individual bits can’t be erased and written to again after a while. Flash memory has a limited number of times that data can be written to a location.

2. SSDs are expensive: The price per gigabyte is significantly more expensive than traditional drives. For example, a 2TB HDD costs around $100, which is exactly how much a 60GB SSD costs. You get way more storage for your buck with an HDD. SSDs are more expensive to produce, so the MSRP tends to be higher than that of HDDs.

3. SSDs has lower storage capacity: Compared to HDDs, SSDs have much less storage capacity. SSDs have not been made in real high capacities yet to my knowledge. So, you will probably have to spend more money for more storage.


Also, regarding TEMPDB please remember that tempdb is write heavy, and SSD's have a limited write life. I'm not saying that this can't work, people are doing it, I'm just saying it is something you need to be aware of. :-D

"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"
Dave Poole
Dave Poole
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17244 Visits: 3403
The thing with traditional HDDs is that not all the space is usable due to the need for multiple spindles to deliver throughput so it isn't as simple a case as saying HDD = £x per unit and SSD = £y per unit.

If you are using SSD for locally attached storage then fantastic. If they are going in a SAN then remember the SAN header will probably get overwhelmed by the throughput.

LinkedIn Profile
www.simple-talk.com
cdonlan 18448
cdonlan 18448
SSC-Enthusiastic
SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)SSC-Enthusiastic (103 reputation)

Group: General Forum Members
Points: 103 Visits: 283
David.Poole (1/3/2013)
The thing with traditional HDDs is that not all the space is usable due to the need for multiple spindles to deliver throughput so it isn't as simple a case as saying HDD = £x per unit and SSD = £y per unit.

If you are using SSD for locally attached storage then fantastic. If they are going in a SAN then remember the SAN header will probably get overwhelmed by the throughput.


This is an excellent point, but probably manageable from the SAN's buffer. One of the first things I learned was that this was usually set too low for SQL Server. It varies from product to product as I recall.
Dave Poole
Dave Poole
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17244 Visits: 3403
Forgot to mention that pre SQL2012 putting TempDB on local storage in a cluster was possible but definitely not supported or recommended by Microsoft.

LinkedIn Profile
www.simple-talk.com
Summer90
Summer90
SSCertifiable
SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)

Group: General Forum Members
Points: 7487 Visits: 3831
I have heard some horror stories a year or so ago about SSDs.... the one guy I know who works for MSFT as a SQL Server guru said, at that point in time he'd shy away from them. He knew of a couple of stories that they were very fast but all of a sudden they failed. Again, that was a couple of years ago. I know we use it for one of our high end Oracle DBs but it was very expensive when we got it.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search