Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQLServerCentral.com
»
Editorials
»
All Flash
12 posts, Page 1 of 2
1
2
»»
All Flash
Rate Topic
Display Mode
Topic Options
Author
Message
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Thursday, January 03, 2013 12:14 AM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 11:20 AM
Points: 31,437,
Visits: 13,752
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
Post #1402208
call.copse
call.copse
Posted Thursday, January 03, 2013 2:50 AM
Ten Centuries
Group: General Forum Members
Last Login: 2 days ago @ 2:48 AM
Points: 1,088,
Visits: 693
Nice idea (the tempdb thing) - I can think of one inherited application this could easily buy some time with. I'll investigate, cheers.
Post #1402255
cdonlan 18448
cdonlan 18448
Posted Thursday, January 03, 2013 7:52 AM
SSC Rookie
Group: General Forum Members
Last Login: Friday, April 19, 2013 8:44 AM
Points: 45,
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.
Post #1402393
SQLRNNR
SQLRNNR
Posted Thursday, January 03, 2013 9:32 AM
SSCoach
Group: General Forum Members
Last Login: 2 days ago @ 10:25 AM
Points: 18,754,
Visits: 12,337
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 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1402450
Miles Neale
Miles Neale
Posted Thursday, January 03, 2013 12:23 PM
SSCommitted
Group: General Forum Members
Last Login: Monday, May 20, 2013 9:51 AM
Points: 1,891,
Visits: 936
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!
Post #1402503
TravisDBA
TravisDBA
Posted Thursday, January 03, 2013 2:32 PM
Ten Centuries
Group: General Forum Members
Last Login: Thursday, May 09, 2013 9:23 AM
Points: 1,288,
Visits: 2,996
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.
"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...
"
Post #1402571
David.Poole
David.Poole
Posted Thursday, January 03, 2013 4:44 PM
SSCrazy
Group: General Forum Members
Last Login: 2 days ago @ 8:46 AM
Points: 2,750,
Visits: 1,410
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
Post #1402614
cdonlan 18448
cdonlan 18448
Posted Friday, January 04, 2013 7:58 AM
SSC Rookie
Group: General Forum Members
Last Login: Friday, April 19, 2013 8:44 AM
Points: 45,
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.
Post #1402890
David.Poole
David.Poole
Posted Friday, January 04, 2013 10:30 AM
SSCrazy
Group: General Forum Members
Last Login: 2 days ago @ 8:46 AM
Points: 2,750,
Visits: 1,410
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
Post #1403001
Markus
Markus
Posted Friday, January 04, 2013 11:05 AM
Ten Centuries
Group: General Forum Members
Last Login: 2 days ago @ 6:12 AM
Points: 1,048,
Visits: 2,217
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.
Post #1403025
« Prev Topic
|
Next Topic »
12 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.