You can configure SQL Server Profiler to extract Deadlock graph events to a single file that contains all Deadlock graph events, or to separate files. SQL Server Profiler can extract the XML document to a deadlock XML (.xdl) file which you can view later in SQL Server Management Studio. This event class populates the TextData data column in the trace with XML data about the process and objects that are involved in the deadlock. To trace deadlock events, add the Deadlock graph event class to a trace. If that doesn't reveal anything, you can analyze deadlocks using the SQL Server Profiler: You should analyze your process and see if there are scenarios where locks could be acquired in a different order. It applies here because DELETE and UPDATE statements implicitely acquire locks on the rows or index range or table (depending on what the engine deems appropriate). How would acquiring locks in the same order apply here? Have you got any advice on how he would change his SQL to do that?ĭeadlocks are always the same, no matter what environment: two processes (say A & B) acquire multiple locks (say X & Y) in a different order so that A is waiting for Y and B is waiting for X while A is holding X and B is holding Y.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |