Are the posted questions getting worse?

  • dwain.c (4/26/2012)


    You mean I gotta remember who and when?

    I'm lucky sometimes if I can remember the day of the week.

    Nope... just quote the thread by hitting the quote button instead of the reply button.

    --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 (4/26/2012)


    dwain.c (4/26/2012)


    You mean I gotta remember who and when?

    I'm lucky sometimes if I can remember the day of the week.

    Nope... just quote the thread by hitting the quote button instead of the reply button.

    Excuse my Homer Simpson moment... Doh!


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St

  • dwain.c (4/26/2012)


    Jeff Moden (4/26/2012)


    dwain.c (4/26/2012)


    You mean I gotta remember who and when?

    I'm lucky sometimes if I can remember the day of the week.

    Nope... just quote the thread by hitting the quote button instead of the reply button.

    Excuse my Homer Simpson moment... Doh!

    Oh my... Is it really that bad?

    Edit: 'Or my' followed by THREE fullstops.

  • Revenant (4/26/2012)


    dwain.c (4/26/2012)


    Jeff Moden (4/26/2012)


    dwain.c (4/26/2012)


    You mean I gotta remember who and when?

    I'm lucky sometimes if I can remember the day of the week.

    Nope... just quote the thread by hitting the quote button instead of the reply button.

    Excuse my Homer Simpson moment... Doh!

    Oh my... Is it really that bad?

    Edit: 'Or my' followed by THREE fullstops.

    Remember, I live in Bangkok... It depends on what was on the agenda the night before. 🙂


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St

  • I have a question: How can there be a past edition of DBCC TIMEWARP?

    Conceptually, I thought that there was only one version that was and is and ever will be. Unless you set something other than the default value for optional parameter 13 (or parameter 11 if your ARID points to a reality where the documentation is in base 12). At least that's what I thought those handwritten notes on the back of the Rosetta Stone implied. :unsure:

    __________________________________________________

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

  • dwain.c (4/26/2012)


    You mean I gotta remember who and when?

    I'm lucky sometimes if I can remember the day of the week.

    I'll tell you a little secret:

    most of us posters can't either. We just use the quote button on the right.

    edit: say too late that someone else told you this already

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Alert! To any of you really serious T-SQL folk out there, drinking at this water cooler, that want a real challenge.

    Check out this thread: http://www.sqlservercentral.com/Forums/Topic1290424-392-1.aspx

    Maybe I've overcomplicated it or was thinking too much, but I finally came up with a solution that may work or possibly not. I simply don't know.

    I'm guessing no optimal solution can be done without a CURSOR loop, and then the solution you get depends on how you write the loop!

    I'm pretty darn sure that no one can do it with a single SQL INSERT (although I'd be tickled to be wrong).


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St

  • So Steve, the article I submitted that still needs to be edited wont come out in May at all. Maybe June 2nd week if I am lucky?

    -Roy

  • Jeff Moden (4/26/2012)


    dwain.c (4/26/2012)


    You mean I gotta remember who and when?

    I'm lucky sometimes if I can remember the day of the week.

    Nope... just quote the thread by hitting the quote button instead of the reply button.

    Just beware of the quote bug. Once you get caught up on The Thread, you'll be well versed on it.

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes


    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • Well, I see that Steve is catching up from being in England... I have an article and a QotD being published on 5/10. Plus my UG mtg that night. Plus presenting to Jason's UG that night. Ought to be a busy day.

    For those that would like a tease for the QotD... brush up on the intricacies of using "SELECT *". 😀

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes


    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • dwain.c (4/27/2012)


    Alert! To any of you really serious T-SQL folk out there, drinking at this water cooler, that want a real challenge.

    Check out this thread: http://www.sqlservercentral.com/Forums/Topic1290424-392-1.aspx

    Maybe I've overcomplicated it or was thinking too much, but I finally came up with a solution that may work or possibly not. I simply don't know.

    I'm guessing no optimal solution can be done without a CURSOR loop, and then the solution you get depends on how you write the loop!

    I'm pretty darn sure that no one can do it with a single SQL INSERT (although I'd be tickled to be wrong).

    Hi Dwain,

    First... welcome to The Thread!

    I posted something over there... I think a sliding window, possibly with some of the new analytic functions could solve this issue (requires SQL 2012 for both). Don't want to pursue this further unless that is an option... but I just might do it anyway as a proof-of-concept for it.

    Wayne
    Microsoft Certified Master: SQL Server 2008
    Author - SQL Server T-SQL Recipes


    If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!
    Links:
    For better assistance in answering your questions
    Performance Problems
    Common date/time routines
    Understanding and Using APPLY Part 1 & Part 2

  • Roy Ernest (4/27/2012)


    So Steve, the article I submitted that still needs to be edited wont come out in May at all. Maybe June 2nd week if I am lucky?

    Probably early June, maybe May. I took a glance at it and it looks pretty good. Your writing is getting better, less work for me 🙂

  • WayneS (4/27/2012)


    Well, I see that Steve is catching up from being in England... I have an article and a QotD being published on 5/10. ...

    For those that would like a tease for the QotD... brush up on the intricacies of using "SELECT *". 😀

    Thanks to Steve my 63rd QOD (on Transactions) is scheduled for publication on 16 May.

    Now I just wish I had enough knowledge to write an article

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • bitbucket-25253 (4/27/2012)


    Thanks to Steve my 63rd QOD (on Transactions) is scheduled for publication on 16 May.

    Now I just wish I had enough knowledge to write an article

    You are welcome, and Ha! You certainly have enough knowledge to write an article. It just has to be something you want to do and then you have to focus on teaching the thing you write about to a junior DBA.

    It's not that hard, but it does take a little practice, and a thick skin.

  • Lynn, take care in the 'Accidental DBA' thread, check the OP's history.

    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

Viewing 15 posts - 35,851 through 35,865 (of 66,712 total)

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