Trace flag in deadlock

  • Comments posted to this topic are about the item Trace flag in deadlock

    Ryan
    //All our dreams can come true, if we have the courage to pursue them//

  • Thanks for the question. I got it wrong as I misread 'non-XML' as 'XML'. So, I chose 1222.

    M&M

  • This was removed by the editor as SPAM

  • mohammed moinudheen (9/14/2011)


    Thanks for the question. I got it wrong as I misread 'non-XML' as 'XML'. So, I chose 1222.

    Know what you mean - do'h.

    Still should teach me to read the question at least twice before answering like I was told in school

    -------------------------------Posting Data Etiquette - Jeff Moden [/url]Smart way to ask a questionThere are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand (the world). There is no such thing as a dumb question. ― Carl Sagan I would never join a club that would allow me as a member - Groucho Marx

  • Great question, but I got it wrong because I jumped too quick and didn't properly think it through.

    I deliberately chose 1222 because it "Returns the resources and types of locks that are participating in a deadlock and also the current command affected, in an XML format that does not comply with any XSD schema."

    My wrong :doze:

    _____________________________________________________________________
    [font="Comic Sans MS"]"The difficult tasks we do immediately, the impossible takes a little longer"[/font]

  • DugyC (9/15/2011)


    Great question, but I got it wrong because I jumped too quick and didn't properly think it through.

    I deliberately chose 1222 because it "Returns the resources and types of locks that are participating in a deadlock and also the current command affected, in an XML format that does not comply with any XSD schema."

    My wrong :doze:

    It's a nice question.

    I didn't fall into the trap of choosing 1222, but that was more luck than anything else, as according to the detecting and ending deadlocks page 1222 doesn't produce XML but "an XML-like format". Good old BoL, contradicting itself again. It also claims that SQL 2008 records information in the SQL 2005 error log, which seems unlikely to be correct.

    Tom

  • trouble is 1222 returns the info in a much easier to read format, so we should be encouraging people to use that trace flag rather than 1204.

    thats my point back. 🙂

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

  • It also claims that SQL 2008 records information in the SQL 2005 error log, which seems unlikely to be correct.

    thats why I can't find any deadlock info !

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

  • very good question!!!


    [font="Times New Roman"]rfr.ferrari[/font]
    DBA - SQL Server 2008
    MCITP | MCTS

    remember is live or suffer twice!
    the period you fastest growing is the most difficult period of your life!
  • Good question, thanks for submitting.

    http://brittcluff.blogspot.com/

  • Tom.Thomson (9/15/2011)


    DugyC (9/15/2011)


    Great question, but I got it wrong because I jumped too quick and didn't properly think it through.

    I deliberately chose 1222 because it "Returns the resources and types of locks that are participating in a deadlock and also the current command affected, in an XML format that does not comply with any XSD schema."

    My wrong :doze:

    It's a nice question.

    I didn't fall into the trap of choosing 1222, but that was more luck than anything else, as according to the detecting and ending deadlocks page 1222 doesn't produce XML but "an XML-like format". Good old BoL, contradicting itself again. It also claims that SQL 2008 records information in the SQL 2005 error log, which seems unlikely to be correct.

    Plus, the example of trace flag 1222's output provided on the page Tom mentioned doesn't look anything like XML. I would say that "XML-like" != "XML" (using the non-ANSI "not equal to" operator to avoid formatting hassles caused by the "angle bracket"/"greater than" and "less than" symbols)!

    Jason Wolfkill

  • Thanks for the question.

    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

  • Nice question, thanks

  • Good Question!

  • Good question! Thanks!

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

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