Are the posted questions getting worse?

  • P Jones (1/28/2009)


    Today I'm delighted to see that the article which annoyed me with bad grammar and lack of spell checking has been pulled for plagiarism.

    The original was written in good english so is it a new attempt to disguise plagiarism with bad grammar and spelling to confuse comparison software??

    Got a link to that article?

  • Steve linked to the original article in his editorial today.

    http://www.sqlservercentral.com/articles/career+growth/64632/

    The plagiarised article has been removed.

    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
  • I didn't get to see it. I wish I had. The discussion about it, prior to the plagiarism exposure, was pretty critical.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Grant Fritchey (1/28/2009)


    I didn't get to see it. I wish I had.

    You didn't miss much. I read about half of it and then gave up

    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
  • It was pretty bad. There were some different paragraphs and some different opening sentences of paragraphs, but there were things like "whether its transaction log backups, and XML indexes or whizbang fiber-optic laser beam assemblers." that were copied word for word, and these aren't phrases you likely see.

  • I was working on a whizbang fiber-optic laser beam assembler just the other day. I had to use that phrase in two different documents.

  • Steve Jones - Editor (1/28/2009)


    It was pretty bad. There were some different paragraphs and some different opening sentences of paragraphs, but there were things like "whether its transaction log backups, and XML indexes or whizbang fiber-optic laser beam assemblers." that were copied word for word, and these aren't phrases you likely see.

    Am I the only one talking like that on a daily basis???

    :w00t::D

  • Y'all are pretty sad excuses for mad scientists.... now a whizbang fiber-optic laser beam DISassembler... capable of reducing any target into it's component subatomic particles... resulting in a weapon of such destructive power that there can be NO defense against it.... forcing the rulers of the world to grovel at my feet... making those fools RUE they day they laughed at me !!!

    muahHHHAAAAHAHAHAHAHAHAAAAAAAAAAAAAAAAaaaaaaaaaaaaaaaaaa....

    Sorry.... I digressed... too much sugar this morning.

    What was the topic again?

    __________________________________________________

    Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
    Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills

  • Unfortunately my company cut corners and we had to make due with the standard fiber-optic laser beam assemblers. They just wouldn't spring for the whizbang model. Stinks.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • I'll admit to using Whizbang at some point in my life, but not regularly. At least I hope not.

    I thought about posting a diff of the docs, but I think it's probably stepping over the line.

  • Steve Jones - Editor (1/28/2009)


    I'll admit to using Whizbang at some point in my life, but not regularly. At least I hope not.

    I thought about posting a diff of the docs, but I think it's probably stepping over the line.

    I agree that dumping it down the memory hole is the RIGHT thing to do. Leaving it around and maybe laying out the diff like you said is the more INTERESTING thing.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Maybe, just maybe, some posters could learn to use Google a bit better. Then they wouldn't have to wait for a reply from the elite gurus.

    Like Naked Ape on 11/19, I too want to express a huge amount of gratitude. It's funny - for many, many years now I have always found someone here with the exact same SQL problem I have, and a solution of some sort.

    Even Google ends-up sending here for a solution!

    I've never had the need to post a question because someone else has done so already! Even the magazine has an uncanny timeliness - there's always an article about something I'm working on.

    Even now, Naked Ape expresses my thoughts precisely! Go read it.

    For kicks, I've got 40+ servers in two Data Centers (LA/Miami) running 2000 & 2005, Merge Repl, Trans Repl, 30+ apps, and 100+ databases. I need fast answers, and you folks give them!

    THANK YOU!

  • That's a heck of a compliment. Posts like that make it all worthwhile. Thanks for taking the time to post it.

    --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)

  • Heh... whad'ya do there, Lynn? Pull a nose hair? Or dislodge a pork chop? 😛

    --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 - 961 through 975 (of 66,712 total)

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