InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 15:01:23 GMT20http://www.sqlservercentral.com/Forums/Topic812033-263-1.aspxI know this is an old post but I had to say "Hear Here!" to it. Great post Tony. Phil is absolutely correct about how even the worst code on certain challenges simply blows away what a lot of folks buy hotter iron for... and the hotter iron frequently doesn't work at all.Here's to all those folks that go the extra mile in code! Well done! {insert sound of someone clinking a beer and drinking it heartily}Sat, 31 Jul 2010 19:56:29 GMTJeff Modenhttp://www.sqlservercentral.com/Forums/Topic812033-263-1.aspxHi TonyYou speak right out of my heart. In my opinion to write faster code is not only a question of skills but also a [i]mindset[/i]. To write tuned code is something people should internalize.The best tuning is [b]pro[/b]active and done by the architecture and system design! Tuning when a system became slow is [b]re[/b]active and often ends up with hacks and a "hope the performance is enough, for now" solution.GreetsFloSun, 01 Nov 2009 11:31:40 GMTFlorian Reischlhttp://www.sqlservercentral.com/Forums/Topic812033-263-1.aspxExcellent points.I think that you ought to try to tune your code, you ought to go back and refactor it when you can. However deadlines, and time pressures can force you to compromise. At some point, it does make sense to throw hardware at it. In web development, where you can deploy another server and scale out, I think that it's harder to spend a lot of time tuning when for $2-3k you can throw a lot of hardware into 1 or 2 more servers. If a developer costs $70k, then you can eat up $2k of time quickly.The issue with many web developers is also talent. So many programmers don't know how to tightly tune code.In SQL Server, you have a single server. To scale up, it's replace a server, often with much more hardware and it can be $10k. So it makes more sense to spend time tuning. There are still limits. You can still spend too much time tuning and not get new development done, but it's more worth it since a new server costs more $$$. You also will run into scale limits. At some point you can't buy a bigger DB server to handle the load from poor code.In either case, developers (SQL or otherwise) need to learn more about better coding techniques. Learn how to write better code that performs better with less resources.Sun, 01 Nov 2009 10:50:02 GMTSteve Jones - SSC Editorhttp://www.sqlservercentral.com/Forums/Topic812033-263-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/Editorial/68655/">The Rich Rewards of Tuning SQL</A>[/B]Sat, 31 Oct 2009 11:36:36 GMTTony Davis