Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

what's with all the "query help"? Expand / Collapse
Author
Message
Posted Tuesday, February 19, 2013 3:22 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 3:45 PM
Points: 1,793, Visits: 5,793
Why, oh why do so many people looking for help think that "query help" is a good title to get people interested in their topic?

If you have a pain in your chest, do you go to the doctor and shout "body help" ?

Come on people, make your topic title relevant and informative, please!


MM


  • MMGrid Addin
  • MMNose Addin


  • Forum Etiquette: How to post Reporting Services problems
  • Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
  • How to Post Performance Problems - by Gail Shaw

  • Post #1421873
    Posted Wednesday, February 20, 2013 12:28 AM


    SSCrazy

    SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

    Group: General Forum Members
    Last Login: Today @ 5:38 AM
    Points: 2,379, Visits: 7,579
    mister.magoo (2/19/2013)
    If you have a pain in your chest, do you go to the doctor and shout "body help" ?


    Nope, you call up and shout "Urgent! Body Help Now!".

    Then one of three things: -
    • hang up and never come back again

    • Stay on the line and complain that they're stupid and not helpful when they ask follow up questions

    • Call them rude for explaining how to help yourself



    Not a DBA, just trying to learn

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better, quicker answers on SQL Server performance related questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/



    If you litter your database queries with nolock query hints, are you aware of the side effects?
    Try reading a few of these links...

    (*) Missing rows with nolock
    (*) Allocation order scans with nolock
    (*) Consistency issues with nolock
    (*) Transient Corruption Errors in SQL Server error log caused by nolock
    (*) Dirty reads, read errors, reading rows twice and missing rows with nolock


    LinkedIn | Blog coming soon (for sufficiently large values of "soon" )!
    Post #1421948
    « Prev Topic | Next Topic »

    Add to briefcase

    Permissions Expand / Collapse