﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Editorials / SQLServerCentral.com  / Challenge Yourself / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Thu, 23 May 2013 19:52:01 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Challenge Yourself</title><link>http://www.sqlservercentral.com/Forums/Topic1366247-263-1.aspx</link><description>Understand, but I think the term "iron" rule, was what threw some people like myself.:-D</description><pubDate>Tue, 02 Oct 2012 11:15:15 GMT</pubDate><dc:creator>TravisDBA</dc:creator></item><item><title>RE: Challenge Yourself</title><link>http://www.sqlservercentral.com/Forums/Topic1366247-263-1.aspx</link><description>Setting down a rule is intended to do just that, set a rule. However I do understand that there will be exceptions to the rule. What I didn't want was every person thinking exception first.</description><pubDate>Tue, 02 Oct 2012 08:53:52 GMT</pubDate><dc:creator>Steve Jones - SSC Editor</dc:creator></item><item><title>RE: Challenge Yourself</title><link>http://www.sqlservercentral.com/Forums/Topic1366247-263-1.aspx</link><description>How can you say to never do something, turn around and do it and they say it isn't hypocritical? Of course it is and this applies to any topic where a person preaches 'this' and does 'that'. This editorial should have never been written much less posted again. This article started off being about a rule that couldn't be enforced so the title should have been more about being flexible but instead it seems to lead down a road of denial.We can all agree that doing things right the first time is very important as we can agree that standards and rules are. However, rules were made to be broken and I'd like to suggest that instead of saying "you can never do this" try implementing some sort of justification process. If someone insist they need to use a cursor for a given task make them justify it. If others in the room can suggest a more efficient/effective solution then no cursor. If nobody has anything to offer then...</description><pubDate>Mon, 01 Oct 2012 12:43:08 GMT</pubDate><dc:creator>jfogel</dc:creator></item><item><title>RE: Challenge Yourself</title><link>http://www.sqlservercentral.com/Forums/Topic1366247-263-1.aspx</link><description>I am curious on the rule against temp tables. Is that in preference for work tables?</description><pubDate>Mon, 01 Oct 2012 09:35:30 GMT</pubDate><dc:creator>srienstr</dc:creator></item><item><title>RE: Challenge Yourself</title><link>http://www.sqlservercentral.com/Forums/Topic1366247-263-1.aspx</link><description>"I used to tell all junior DBAs working for me that no cursors or temp tables were allowed. It was an iron rule for them to work within in the SQL Server v6.5 days and they needed to abide by it. Then one of them saw me using a cursor to perform some administrative update and asked me why. "I personally do not make "ironclad rules" like this for a very obvious reason. It sounds dictatorial.  I agree their use should be discouraged as a front line go to tool, but I think establishing an "iron rule" to not use them is a bit much.:-D</description><pubDate>Mon, 01 Oct 2012 09:15:27 GMT</pubDate><dc:creator>TravisDBA</dc:creator></item><item><title>Challenge Yourself</title><link>http://www.sqlservercentral.com/Forums/Topic1366247-263-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/articles/Editorial/93410/"&gt;Challenge Yourself&lt;/A&gt;[/B]</description><pubDate>Sun, 30 Sep 2012 04:40:52 GMT</pubDate><dc:creator>Steve Jones - SSC Editor</dc:creator></item></channel></rss>