Are the posted questions getting worse?

  • Alan.B (5/1/2015)


    Luis Cazares (5/1/2015)


    Jeff Moden (5/1/2015)


    I had a rare and wonderful opportunity, today. Luis is in town and I finally got to meet him and have lunch with both him and Ed Wagner. What a treat and I get to scratch another name off my bucket list.

    It was my pleasure to meet both of you. I hope to start scratching names off my bucket list now that I'll be traveling on this side of the border. 😀

    There's plenty of good bbq and local beer here in Chicago this time of the year. Just sayin'.

    Chicago isn't that far away for us. I'll keep that in mind when shopping for SQL Saturdays.

  • FYI, Erland Sommarskog has a new set of articles on Error Handling in T-SQL that y'all might be interested in. It starts here, http://www.sommarskog.se/error_handling/Part1.html.

  • And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

  • Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    Update statistics?

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

  • Koen Verbeeck (5/4/2015)


    Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    Update statistics?

    Improve performance without a code change? That's a good one. I typically find that most performance problems I encounter are due to design decisions and poor code. If you can't change the code, that doesn't leave much room for improvement.

  • Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    Yeah, they just want the syntax for the "Run Faster" switch that we all keep hidden from them.

    "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 (5/4/2015)


    Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    Yeah, they just want the syntax for the "Run Faster" switch that we all keep hidden from them.

    Isn't the supposed to be NOLOCK???

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    Truncate Table!!

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • SQLRNNR (5/4/2015)


    Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    Truncate Table!!

    Silly me...I didn't even think of that. No code change + faster performance = requirements met. :hehe:

  • Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    What's the link for that thread? I'm just curious...

    --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 (5/4/2015)


    Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    What's the link for that thread? I'm just curious...

    Here: http://www.sqlservercentral.com/Forums/Topic1682107-3077-1.aspx

  • Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    Sometimes, improving the indexing is the only option available. Supporting a product where most of the code is embedded in the code and requires approval to make changes, then needs to go through extensive testing and approval processes, you do what you can where you can.

  • Lynn Pettis (5/4/2015)


    Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    Sometimes, improving the indexing is the only option available. Supporting a product where most of the code is embedded in the code and requires approval to make changes, then needs to go through extensive testing and approval processes, you do what you can where you can.

    Wow that person is way too snarky to the people who are trying to help him. It doesn't seem like any amount of indexing is going to help a flawed implementation. How can indexing fix the problem? It isn't a problem of data retrieval being too slow. It is a problem of pushing all the data over the network when only 1 row is needed. I also don't understand why changing a single query to execute a proc on another server requires "thousands" of stored proc changes. If that is true, which I highly doubt, then they need a complete system rewrite because everything is far too tightly coupled to be successful anyway.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Lynn Pettis (5/4/2015)


    Jeff Moden (5/4/2015)


    Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    What's the link for that thread? I'm just curious...

    Here: http://www.sqlservercentral.com/Forums/Topic1682107-3077-1.aspx

    Ah.... THAT one!

    It's a little weird. When I started reading that, I thought the troublesome code was in a single proc. Now the OP is saying it's in thousands of places.

    I'd like to see someone get to the bottom of the Ops problem there. Not sure the OP totally understands it but looks like a couple of people might have gotten under his skin. I'm thinking that there's a misunderstanding there and, until the misunderstanding is cleared up, it might be better to just back off. Trapped animal syndrome starting on that thread.

    --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 (5/4/2015)


    Lynn Pettis (5/4/2015)


    Jeff Moden (5/4/2015)


    Jack Corbett (5/4/2015)


    And for back to back posts to the thread. I really can't stand it when an OP says something like:

    Please help me fix this poorly performing query, but without any code changes.

    So how am I supposed to help? Maybe with some indexing tips, but, in my opinion, that's a code change.

    What's the link for that thread? I'm just curious...

    Here: http://www.sqlservercentral.com/Forums/Topic1682107-3077-1.aspx

    Ah.... THAT one!

    It's a little weird. When I started reading that, I thought the troublesome code was in a single proc. Now the OP is saying it's in thousands of places.

    I'd like to see someone get to the bottom of the Ops problem there. Not sure the OP totally understands it but looks like a couple of people might have gotten under his skin. I'm thinking that there's a misunderstanding there and, until the misunderstanding is cleared up, it might be better to just back off. Trapped animal syndrome starting on that thread.

    Poke Poke Poke :satisfied:

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

Viewing 15 posts - 48,331 through 48,345 (of 66,569 total)

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