Are the posted answers getting worse?

  • OK, we've had fun bashing frustrating posters & topics.

    But to be fair, we should hold ourselves much more accountable than them (after all, we do know better). So this topic is devoted to pointing out our own mistakes, blunders and bloopers.

    The rules: You can only point out your own flaws and failings (or someone's whom you are are on good enough terms to get away with it 🙂 ). No mere typos or grammar errors either. This is for really dumb, stupid things that either:

    1) Make you look like an idiot, or

    2) Leaves everyone scratching their heads, saying "what the heck was that?", or

    3) Completely contradict your own point, or

    4) Is the opposite of what you tell everyone else to do.

    And yes, I'll go first...

    -------------------------------------------------------------------------

    Who does this guy "RBarryYoung" think he is? He can't even get a simple query right. Check this out: here.

    Man, what a bonehead!

    (Edit: Believe it or not, I got the link wrong too!)

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.
    [/font]
    [font="Verdana"] "Performance is our middle name."[/font]

  • i really like the answers that point to a link with letmegooglethatforyou.com...i really think it makes people think twice.

    so yeah, our answers might be a little arrogant when we do that...but hey.

    really, i think there are only like 6 questions that keep getting repeated over 90 percent of the posts, and the other 10% are the ones that we enjoy.

    The most common? i think are:

    1. not understanding how to get a datetime or dateadd value in a query?

    2. pivot table/crosstab/rows-to-columns?

    3. how do i fill in non-existant data with a Tally Table?

    4. comma delimit a bunch of fields or columns into a single field?

    5. how do i find out who deleted/updated something?

    6. what's the answer to my homework?

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • Well, I agree with your list Lowell. And I do use that link sometimes myself (mostly with my kids). But neither of those are the point of this topic. The point is, find a reply that you made that you wish you never had and point it out here. 😀

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.
    [/font]
    [font="Verdana"] "Performance is our middle name."[/font]

  • As it may difficult to critique myself. I decided that I'll let any of the top 15 forum leaders have the honor of pointing out my mistakes. I have faith in their knowledge and abilities and feel that they are best to critique me on this forum.

    Have fun, be kind, yet firm.

  • RBarryYoung (1/21/2009)


    Man, what a bonehead!

    And all that time.... I thought it was a helmet. 😉

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • BWAA-HAA!! I'd like to see a thread on nominations as to who can fire the best pork chops and it can't be yourself! Here's a recent post that would fit the bill...

    http://www.sqlservercentral.com/Forums/Topic641279-8-1.aspx?Update=1

    That's gotta be one of the driest, on the mark pork chops I've ever seen. 😛

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Jeff Moden (1/21/2009)


    RBarryYoung (1/21/2009)


    Man, what a bonehead!

    And all that time.... I thought it was a helmet. 😉

    No, no, no, dude! The helmet is to cover-up my bonehead.

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.
    [/font]
    [font="Verdana"] "Performance is our middle name."[/font]

  • Lowell (1/21/2009)


    really, i think there are only like 6 questions that keep getting repeated over 90 percent of the posts, and the other 10% are the ones that we enjoy.

    The most common? i think are:

    1. not understanding how to get a datetime or dateadd value in a query?

    2. pivot table/crosstab/rows-to-columns?

    3. how do i fill in non-existant data with a Tally Table?

    4. comma delimit a bunch of fields or columns into a single field?

    5. how do i find out who deleted/updated something?

    6. what's the answer to my homework?

    good list, Steve should put this as a Sticky on top of every section 🙂

    -------------------------------------------------------------
    "It takes 15 minutes to learn the game and a lifetime to master"
    "Share your knowledge. It's a way to achieve immortality."

  • Lowell (1/21/2009)


    really, i think there are only like 6 questions that keep getting repeated over 90 percent of the posts, and the other 10% are the ones that we enjoy.

    The most common? i think are:

    1. not understanding how to get a datetime or dateadd value in a query?

    2. pivot table/crosstab/rows-to-columns?

    3. how do i fill in non-existant data with a Tally Table?

    4. comma delimit a bunch of fields or columns into a single field?

    5. how do i find out who deleted/updated something?

    6. what's the answer to my homework?

    Number 4 should be modified, or we need an additional one:

    4a. split a column with comma-delimited values into multiple columns

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.
    [/font]
    [font="Verdana"] "Performance is our middle name."[/font]

  • I probably have a few good ones, maybe more in articles than answers, but I'd like to think that most of us have good answers, often backing each other up.

    I don't see a lot of bad answers from people, sometimes incomplete or not thought out, or leading the OP down a path that will get them into trouble by answering the question and not asking for more details.

    If you find some of mine, be sure to post them. I'm sure I've made quite a few mistakes. No editorial links, please, I hear about mistakes there quite often already.:w00t:

  • Lowell (1/21/2009)


    really, i think there are only like 6 questions that keep getting repeated over 90 percent of the posts, and the other 10% are the ones that we enjoy.

    You missed one.

    7) My transaction log's filled the drive up, how do I get rid of it?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • My all time favorite... "I have 3 tables... yada-yada-yada... how do I join them?" I have to admit, I don't even bother answering those anymore. Not a code mistake, but qualifies as a mistake, none the less.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Guess I'll be the one to break the "real" ice on this thread...

    It's not an answer on a thread that I really messed up on... no... it's much worse. I did it in an article and I'm in the process of rewriting the article to fix it. It's in the "running total" article where, as usual, I "prove" something with an actual code example. Well, finally, someone was able to produce a code proof where something I "proved with code" doesn't actually work exactly the way I said it would 100% of the time. You cannot rely on a Clustered Index Hint to take the place of an ORDER BY like I said it would. So... I gotta wipe the egg off my face on that one and fix it.

    The ironic part about all of this is that very example actually strengthens the argument that the quirky update does always work as advertised. I'm going to make sure to include that, as well.

    This does bring up a good subject... I've seen lots of folks take the advice of artcles where they don't actually use code to prove a point... it's all part of the "SQL Clone" syndrome where if some well known author posts some code with, say, a triangular join in it, people will still copy and post that code as a viable solution even though it'll eat the face off of a computer in a high scale environment.

    A long time ago, Sergiy once made a comment to me that has really stuck with me. I try to practice it all the time especially in artcles and the threads on this post. It's damned good advice that we should all follow... [font="Arial Black"]"A Developer must not guess... a Developer must KNOW." [/font] Actually, that sounds like a softer and better title to an aticle explaining that problem than the "The 'SQL Clone' Epidemic". 😉

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Jeff Moden (1/25/2009)


    The ironic part about all of this is that very example actually strengthens the argument that the quirky update does always work as advertised. I'm going to make sure to include that, as well.

    If I may...

    Even that is only in the current versions of SQL. Since it's not guaranteed (and if you want more info on that Jeff, please mail me, I can't post it here), there's nothing to stop a change in a future version breaking that ordered update.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • GilaMonster (1/25/2009)


    Jeff Moden (1/25/2009)


    The ironic part about all of this is that very example actually strengthens the argument that the quirky update does always work as advertised. I'm going to make sure to include that, as well.

    If I may...

    Even that is only in the current versions of SQL. Since it's not guaranteed (and if you want more info on that Jeff, please mail me, I can't post it here), there's nothing to stop a change in a future version breaking that ordered update.

    Yeap... understood... but I've heard that argument before. The real fact of the matter is that even well documented features can change without warning. Look what happened with the privs on sp_MakeWebTask in 2k sp4. No warning... they just changed it and it broke a lot of code. The backup to such a "break" for the quirky update method is that the ORDER BY method also works although it works at about half the speed. Still, that's a whole lot faster than a cursor.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 15 posts - 1 through 15 (of 46 total)

You must be logged in to reply to this topic. Login to reply