Hi,
We've been getting some deadlocks on our production box.
I've turned on the 3605 and 1204 flags and I've found an error in the
errorlog:
I think the key lines I'm concerned about are these:
Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
0x2
Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags:
0x2
This appears to be locks on the sysobjects table in my database?
Both processes appear to be running this commands:
Input Buf: RPC Event: sp_prepexec;1
Does anyone have an idea where I can go from here? I was assuming I'd be
getting a lock on a user table making it easier to debug.
The only major change recently, is a view that joins 3 tables together
partitioned on date.
Any ideas appreciated.
Nick
Hi Nick
You may want to post the full details for each node. Alternatively you may
want to see if sp_blocker_pss80 produces clearer output
http://support.microsoft.com/kb/271509/EN-US/
John
"Nick Dawson" wrote:
> Hi,
> We've been getting some deadlocks on our production box.
> I've turned on the 3605 and 1204 flags and I've found an error in the
> errorlog:
> I think the key lines I'm concerned about are these:
> Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
> 0x2
> Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags:
> 0x2
> This appears to be locks on the sysobjects table in my database?
> Both processes appear to be running this commands:
> Input Buf: RPC Event: sp_prepexec;1
> Does anyone have an idea where I can go from here? I was assuming I'd be
> getting a lock on a user table making it easier to debug.
> The only major change recently, is a view that joins 3 tables together
> partitioned on date.
> Any ideas appreciated.
> Nick
>
>
Showing posts with label error. Show all posts
Showing posts with label error. Show all posts
Thursday, March 29, 2012
Deadlocks on sysobjects
Hi,
We've been getting some deadlocks on our production box.
I've turned on the 3605 and 1204 flags and I've found an error in the
errorlog:
I think the key lines I'm concerned about are these:
Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
0x2
Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags:
0x2
This appears to be locks on the sysobjects table in my database?
Both processes appear to be running this commands:
Input Buf: RPC Event: sp_prepexec;1
Does anyone have an idea where I can go from here? I was assuming I'd be
getting a lock on a user table making it easier to debug.
The only major change recently, is a view that joins 3 tables together
partitioned on date.
Any ideas appreciated.
NickHi Nick
You may want to post the full details for each node. Alternatively you may
want to see if sp_blocker_pss80 produces clearer output
http://support.microsoft.com/kb/271509/EN-US/
John
"Nick Dawson" wrote:
> Hi,
> We've been getting some deadlocks on our production box.
> I've turned on the 3605 and 1204 flags and I've found an error in the
> errorlog:
> I think the key lines I'm concerned about are these:
> Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
> 0x2
> Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags:
> 0x2
> This appears to be locks on the sysobjects table in my database?
> Both processes appear to be running this commands:
> Input Buf: RPC Event: sp_prepexec;1
> Does anyone have an idea where I can go from here? I was assuming I'd be
> getting a lock on a user table making it easier to debug.
> The only major change recently, is a view that joins 3 tables together
> partitioned on date.
> Any ideas appreciated.
> Nick
>
>sql
We've been getting some deadlocks on our production box.
I've turned on the 3605 and 1204 flags and I've found an error in the
errorlog:
I think the key lines I'm concerned about are these:
Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
0x2
Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags:
0x2
This appears to be locks on the sysobjects table in my database?
Both processes appear to be running this commands:
Input Buf: RPC Event: sp_prepexec;1
Does anyone have an idea where I can go from here? I was assuming I'd be
getting a lock on a user table making it easier to debug.
The only major change recently, is a view that joins 3 tables together
partitioned on date.
Any ideas appreciated.
NickHi Nick
You may want to post the full details for each node. Alternatively you may
want to see if sp_blocker_pss80 produces clearer output
http://support.microsoft.com/kb/271509/EN-US/
John
"Nick Dawson" wrote:
> Hi,
> We've been getting some deadlocks on our production box.
> I've turned on the 3605 and 1204 flags and I've found an error in the
> errorlog:
> I think the key lines I'm concerned about are these:
> Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
> 0x2
> Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags:
> 0x2
> This appears to be locks on the sysobjects table in my database?
> Both processes appear to be running this commands:
> Input Buf: RPC Event: sp_prepexec;1
> Does anyone have an idea where I can go from here? I was assuming I'd be
> getting a lock on a user table making it easier to debug.
> The only major change recently, is a view that joins 3 tables together
> partitioned on date.
> Any ideas appreciated.
> Nick
>
>sql
Deadlocks on sysobjects
Hi,
We've been getting some deadlocks on our production box.
I've turned on the 3605 and 1204 flags and I've found an error in the
errorlog:
I think the key lines I'm concerned about are these:
Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
0x2
Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags:
0x2
This appears to be locks on the sysobjects table in my database?
Both processes appear to be running this commands:
Input Buf: RPC Event: sp_prepexec;1
Does anyone have an idea where I can go from here? I was assuming I'd be
getting a lock on a user table making it easier to debug.
The only major change recently, is a view that joins 3 tables together
partitioned on date.
Any ideas appreciated.
NickHi Nick
You may want to post the full details for each node. Alternatively you may
want to see if sp_blocker_pss80 produces clearer output
http://support.microsoft.com/kb/271509/EN-US/
John
"Nick Dawson" wrote:
> Hi,
> We've been getting some deadlocks on our production box.
> I've turned on the 3605 and 1204 flags and I've found an error in the
> errorlog:
> I think the key lines I'm concerned about are these:
> Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
> 0x2
> Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags
:
> 0x2
> This appears to be locks on the sysobjects table in my database?
> Both processes appear to be running this commands:
> Input Buf: RPC Event: sp_prepexec;1
> Does anyone have an idea where I can go from here? I was assuming I'd be
> getting a lock on a user table making it easier to debug.
> The only major change recently, is a view that joins 3 tables together
> partitioned on date.
> Any ideas appreciated.
> Nick
>
>
We've been getting some deadlocks on our production box.
I've turned on the 3605 and 1204 flags and I've found an error in the
errorlog:
I think the key lines I'm concerned about are these:
Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
0x2
Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags:
0x2
This appears to be locks on the sysobjects table in my database?
Both processes appear to be running this commands:
Input Buf: RPC Event: sp_prepexec;1
Does anyone have an idea where I can go from here? I was assuming I'd be
getting a lock on a user table making it easier to debug.
The only major change recently, is a view that joins 3 tables together
partitioned on date.
Any ideas appreciated.
NickHi Nick
You may want to post the full details for each node. Alternatively you may
want to see if sp_blocker_pss80 produces clearer output
http://support.microsoft.com/kb/271509/EN-US/
John
"Nick Dawson" wrote:
> Hi,
> We've been getting some deadlocks on our production box.
> I've turned on the 3605 and 1204 flags and I've found an error in the
> errorlog:
> I think the key lines I'm concerned about are these:
> Process 1 -> PAG: 7:1:784316 CleanCnt:2 Mode: IX Flags:
> 0x2
> Process 2 -> PAG: 7:1:812678 CleanCnt:2 Mode: SIU Flags
:
> 0x2
> This appears to be locks on the sysobjects table in my database?
> Both processes appear to be running this commands:
> Input Buf: RPC Event: sp_prepexec;1
> Does anyone have an idea where I can go from here? I was assuming I'd be
> getting a lock on a user table making it easier to debug.
> The only major change recently, is a view that joins 3 tables together
> partitioned on date.
> Any ideas appreciated.
> Nick
>
>
Deadlocks Information.
When a deadlock occurs, the system dumps a bunch of diagnostics
information into its error log and ends up looking like the excerpt
below. Does an application exist anywhere that parses this stuff and
tells me exactly what tables/indexes/etc... were involved in the deadlock?
Deadlock encountered ... Printing deadlock information
Wait-for graph
Node:1
KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
Grant List 3::
Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
ECID:0
SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
Input Buf: RPC Event: pr_Sproc1;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)
Value:0x6847aac0 Cost0/0)
Node:2
TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
Grant List 3::
Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
ECID:0
SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
Input Buf: RPC Event: pr_Sproc2;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec0x78181580)
Value:0x57f04c80 Cost0/1ED4)
Victim Resource Owner:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
Value:0x6847aac0 Cost0/0)There is no application to do the parsing, afaik.
Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
good description of how to interpret the information
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
> Value:0x6847aac0 Cost0/0)
>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec0x78181580)
> Value:0x57f04c80 Cost0/1ED4)
> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
> Value:0x6847aac0 Cost0/0)
>|||Frank:
If you use profiler, you can get a graphical representation of the
objects/sessions involved in the deadlock. Also, the new TF-1222 provides
much richer information on the deadlock.
Thanks
--
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
> Value:0x6847aac0 Cost0/0)
>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec0x78181580)
> Value:0x57f04c80 Cost0/1ED4)
> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
> Value:0x6847aac0 Cost0/0)|||Sorry, I should have pointed out that my previous mail is only applicable
for SQL2005.
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sunil Agarwal [MSFT]" <sunila@.onlin.microsoft.com> wrote in message
news:e5BGA%23h6FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Frank:
> If you use profiler, you can get a graphical representation of the
> objects/sessions involved in the deadlock. Also, the new TF-1222 provides
> much richer information on the deadlock.
> Thanks
> --
> Sunil Agarwal (MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Frank Rizzo" <none@.none.com> wrote in message
> news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
>|||Kalen Delaney wrote:
> There is no application to do the parsing, afaik.
> Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
> good description of how to interpret the information
I understand how to interpret them, however, it is a pain. I thought by
now someone had enough of it and wrote something up. Sounds like a
weekend project.
information into its error log and ends up looking like the excerpt
below. Does an application exist anywhere that parses this stuff and
tells me exactly what tables/indexes/etc... were involved in the deadlock?
Deadlock encountered ... Printing deadlock information
Wait-for graph
Node:1
KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
Grant List 3::
Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
ECID:0
SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
Input Buf: RPC Event: pr_Sproc1;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)Value:0x6847aac0 Cost
0/0)Node:2
TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
Grant List 3::
Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
ECID:0
SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
Input Buf: RPC Event: pr_Sproc2;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec
0x78181580)Value:0x57f04c80 Cost
0/1ED4)Victim Resource Owner:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)Value:0x6847aac0 Cost
0/0)There is no application to do the parsing, afaik.Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
good description of how to interpret the information
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)> Value:0x6847aac0 Cost
0/0)>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec
0x78181580)> Value:0x57f04c80 Cost
0/1ED4)> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)> Value:0x6847aac0 Cost
0/0)>|||Frank:
If you use profiler, you can get a graphical representation of the
objects/sessions involved in the deadlock. Also, the new TF-1222 provides
much richer information on the deadlock.
Thanks
--
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)> Value:0x6847aac0 Cost
0/0)>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec
0x78181580)> Value:0x57f04c80 Cost
0/1ED4)> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)> Value:0x6847aac0 Cost
0/0)|||Sorry, I should have pointed out that my previous mail is only applicablefor SQL2005.
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sunil Agarwal [MSFT]" <sunila@.onlin.microsoft.com> wrote in message
news:e5BGA%23h6FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Frank:
> If you use profiler, you can get a graphical representation of the
> objects/sessions involved in the deadlock. Also, the new TF-1222 provides
> much richer information on the deadlock.
> Thanks
> --
> Sunil Agarwal (MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Frank Rizzo" <none@.none.com> wrote in message
> news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
>|||Kalen Delaney wrote:
> There is no application to do the parsing, afaik.
> Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
> good description of how to interpret the information
I understand how to interpret them, however, it is a pain. I thought by
now someone had enough of it and wrote something up. Sounds like a
weekend project.
Deadlocks Information.
When a deadlock occurs, the system dumps a bunch of diagnostics
information into its error log and ends up looking like the excerpt
below. Does an application exist anywhere that parses this stuff and
tells me exactly what tables/indexes/etc... were involved in the deadlock?
Deadlock encountered ... Printing deadlock information
Wait-for graph
Node:1
KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
Grant List 3::
Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
ECID:0
SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
Input Buf: RPC Event: pr_Sproc1;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
Value:0x6847aac0 Cost0/0)
Node:2
TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
Grant List 3::
Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
ECID:0
SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
Input Buf: RPC Event: pr_Sproc2;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec0x78181580)
Value:0x57f04c80 Cost0/1ED4)
Victim Resource Owner:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
Value:0x6847aac0 Cost0/0)
There is no application to do the parsing, afaik.
Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
good description of how to interpret the information
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
> Value:0x6847aac0 Cost0/0)
>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec0x78181580)
> Value:0x57f04c80 Cost0/1ED4)
> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
> Value:0x6847aac0 Cost0/0)
>
|||Frank:
If you use profiler, you can get a graphical representation of the
objects/sessions involved in the deadlock. Also, the new TF-1222 provides
much richer information on the deadlock.
Thanks
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
> Value:0x6847aac0 Cost0/0)
>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec0x78181580)
> Value:0x57f04c80 Cost0/1ED4)
> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec0x576E3580)
> Value:0x6847aac0 Cost0/0)
|||Sorry, I should have pointed out that my previous mail is only applicable
for SQL2005.
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sunil Agarwal [MSFT]" <sunila@.onlin.microsoft.com> wrote in message
news:e5BGA%23h6FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Frank:
> If you use profiler, you can get a graphical representation of the
> objects/sessions involved in the deadlock. Also, the new TF-1222 provides
> much richer information on the deadlock.
> Thanks
> --
> Sunil Agarwal (MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Frank Rizzo" <none@.none.com> wrote in message
> news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
>
|||Kalen Delaney wrote:
> There is no application to do the parsing, afaik.
> Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
> good description of how to interpret the information
I understand how to interpret them, however, it is a pain. I thought by
now someone had enough of it and wrote something up. Sounds like a
weekend project.
information into its error log and ends up looking like the excerpt
below. Does an application exist anywhere that parses this stuff and
tells me exactly what tables/indexes/etc... were involved in the deadlock?
Deadlock encountered ... Printing deadlock information
Wait-for graph
Node:1
KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
Grant List 3::
Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
ECID:0
SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
Input Buf: RPC Event: pr_Sproc1;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)Value:0x6847aac0 Cost
0/0)Node:2
TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
Grant List 3::
Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
ECID:0
SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
Input Buf: RPC Event: pr_Sproc2;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec
0x78181580)Value:0x57f04c80 Cost
0/1ED4)Victim Resource Owner:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)Value:0x6847aac0 Cost
0/0)There is no application to do the parsing, afaik.
Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
good description of how to interpret the information
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)> Value:0x6847aac0 Cost
0/0)>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec
0x78181580)> Value:0x57f04c80 Cost
0/1ED4)> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)> Value:0x6847aac0 Cost
0/0)>
|||Frank:
If you use profiler, you can get a graphical representation of the
objects/sessions involved in the deadlock. Also, the new TF-1222 provides
much richer information on the deadlock.
Thanks
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)> Value:0x6847aac0 Cost
0/0)>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec
0x78181580)> Value:0x57f04c80 Cost
0/1ED4)> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec
0x576E3580)> Value:0x6847aac0 Cost
0/0)|||Sorry, I should have pointed out that my previous mail is only applicable
for SQL2005.
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sunil Agarwal [MSFT]" <sunila@.onlin.microsoft.com> wrote in message
news:e5BGA%23h6FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Frank:
> If you use profiler, you can get a graphical representation of the
> objects/sessions involved in the deadlock. Also, the new TF-1222 provides
> much richer information on the deadlock.
> Thanks
> --
> Sunil Agarwal (MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Frank Rizzo" <none@.none.com> wrote in message
> news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
>
|||Kalen Delaney wrote:
> There is no application to do the parsing, afaik.
> Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
> good description of how to interpret the information
I understand how to interpret them, however, it is a pain. I thought by
now someone had enough of it and wrote something up. Sounds like a
weekend project.
Deadlocks Information.
When a deadlock occurs, the system dumps a bunch of diagnostics
information into its error log and ends up looking like the excerpt
below. Does an application exist anywhere that parses this stuff and
tells me exactly what tables/indexes/etc... were involved in the deadlock?
Deadlock encountered ... Printing deadlock information
Wait-for graph
Node:1
KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
Grant List 3::
Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
ECID:0
SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
Input Buf: RPC Event: pr_Sproc1;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
Value:0x6847aac0 Cost:(0/0)
Node:2
TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
Grant List 3::
Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
ECID:0
SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
Input Buf: RPC Event: pr_Sproc2;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec:(0x78181580)
Value:0x57f04c80 Cost:(0/1ED4)
Victim Resource Owner:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
Value:0x6847aac0 Cost:(0/0)There is no application to do the parsing, afaik.
Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
good description of how to interpret the information
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
> Value:0x6847aac0 Cost:(0/0)
>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec:(0x78181580)
> Value:0x57f04c80 Cost:(0/1ED4)
> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
> Value:0x6847aac0 Cost:(0/0)
>|||Frank:
If you use profiler, you can get a graphical representation of the
objects/sessions involved in the deadlock. Also, the new TF-1222 provides
much richer information on the deadlock.
Thanks
--
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
> Value:0x6847aac0 Cost:(0/0)
>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec:(0x78181580)
> Value:0x57f04c80 Cost:(0/1ED4)
> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
> Value:0x6847aac0 Cost:(0/0)|||Sorry, I should have pointed out that my previous mail is only applicable
for SQL2005.
--
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sunil Agarwal [MSFT]" <sunila@.onlin.microsoft.com> wrote in message
news:e5BGA%23h6FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Frank:
> If you use profiler, you can get a graphical representation of the
> objects/sessions involved in the deadlock. Also, the new TF-1222 provides
> much richer information on the deadlock.
> Thanks
> --
> Sunil Agarwal (MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Frank Rizzo" <none@.none.com> wrote in message
> news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
>> When a deadlock occurs, the system dumps a bunch of diagnostics
>> information into its error log and ends up looking like the excerpt
>> below. Does an application exist anywhere that parses this stuff and
>> tells me exactly what tables/indexes/etc... were involved in the
>> deadlock?
>>
>> Deadlock encountered ... Printing deadlock information
>>
>>
>> Wait-for graph
>>
>>
>> Node:1
>> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
>> Grant List 3::
>> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
>> ECID:0
>> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
>> Input Buf: RPC Event: pr_Sproc1;1
>> Requested By:
>> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
>> Value:0x6847aac0 Cost:(0/0)
>>
>> Node:2
>> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
>> Grant List 3::
>> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
>> ECID:0
>> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
>> Input Buf: RPC Event: pr_Sproc2;1
>> Requested By:
>> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec:(0x78181580)
>> Value:0x57f04c80 Cost:(0/1ED4)
>> Victim Resource Owner:
>> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
>> Value:0x6847aac0 Cost:(0/0)
>|||Kalen Delaney wrote:
> There is no application to do the parsing, afaik.
> Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
> good description of how to interpret the information
I understand how to interpret them, however, it is a pain. I thought by
now someone had enough of it and wrote something up. Sounds like a
weekend project.
information into its error log and ends up looking like the excerpt
below. Does an application exist anywhere that parses this stuff and
tells me exactly what tables/indexes/etc... were involved in the deadlock?
Deadlock encountered ... Printing deadlock information
Wait-for graph
Node:1
KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
Grant List 3::
Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
ECID:0
SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
Input Buf: RPC Event: pr_Sproc1;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
Value:0x6847aac0 Cost:(0/0)
Node:2
TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
Grant List 3::
Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
ECID:0
SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
Input Buf: RPC Event: pr_Sproc2;1
Requested By:
ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec:(0x78181580)
Value:0x57f04c80 Cost:(0/1ED4)
Victim Resource Owner:
ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
Value:0x6847aac0 Cost:(0/0)There is no application to do the parsing, afaik.
Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
good description of how to interpret the information
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
> Value:0x6847aac0 Cost:(0/0)
>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec:(0x78181580)
> Value:0x57f04c80 Cost:(0/1ED4)
> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
> Value:0x6847aac0 Cost:(0/0)
>|||Frank:
If you use profiler, you can get a graphical representation of the
objects/sessions involved in the deadlock. Also, the new TF-1222 provides
much richer information on the deadlock.
Thanks
--
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank Rizzo" <none@.none.com> wrote in message
news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
> When a deadlock occurs, the system dumps a bunch of diagnostics
> information into its error log and ends up looking like the excerpt below.
> Does an application exist anywhere that parses this stuff and tells me
> exactly what tables/indexes/etc... were involved in the deadlock?
>
> Deadlock encountered ... Printing deadlock information
>
>
> Wait-for graph
>
>
> Node:1
> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
> Grant List 3::
> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
> ECID:0
> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
> Input Buf: RPC Event: pr_Sproc1;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
> Value:0x6847aac0 Cost:(0/0)
>
> Node:2
> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
> Grant List 3::
> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
> ECID:0
> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
> Input Buf: RPC Event: pr_Sproc2;1
> Requested By:
> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec:(0x78181580)
> Value:0x57f04c80 Cost:(0/1ED4)
> Victim Resource Owner:
> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
> Value:0x6847aac0 Cost:(0/0)|||Sorry, I should have pointed out that my previous mail is only applicable
for SQL2005.
--
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sunil Agarwal [MSFT]" <sunila@.onlin.microsoft.com> wrote in message
news:e5BGA%23h6FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Frank:
> If you use profiler, you can get a graphical representation of the
> objects/sessions involved in the deadlock. Also, the new TF-1222 provides
> much richer information on the deadlock.
> Thanks
> --
> Sunil Agarwal (MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Frank Rizzo" <none@.none.com> wrote in message
> news:ObGR$%23g6FHA.2092@.TK2MSFTNGP12.phx.gbl...
>> When a deadlock occurs, the system dumps a bunch of diagnostics
>> information into its error log and ends up looking like the excerpt
>> below. Does an application exist anywhere that parses this stuff and
>> tells me exactly what tables/indexes/etc... were involved in the
>> deadlock?
>>
>> Deadlock encountered ... Printing deadlock information
>>
>>
>> Wait-for graph
>>
>>
>> Node:1
>> KEY: 13:1171587312:1 (25009a75c3be) CleanCnt:1 Mode: X Flags: 0x0
>> Grant List 3::
>> Owner:0x45bb0480 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:58
>> ECID:0
>> SPID: 58 ECID: 0 Statement Type: UPDATE Line #: 596
>> Input Buf: RPC Event: pr_Sproc1;1
>> Requested By:
>> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
>> Value:0x6847aac0 Cost:(0/0)
>>
>> Node:2
>> TAB: 13:1203587426 [] CleanCnt:1 Mode: S Flags: 0x0
>> Grant List 3::
>> Owner:0x684935a0 Mode: S Flg:0x0 Ref:1 Life:00000001 SPID:53
>> ECID:0
>> SPID: 53 ECID: 0 Statement Type: SELECT INTO Line #: 579
>> Input Buf: RPC Event: pr_Sproc2;1
>> Requested By:
>> ResType:LockOwner Stype:'OR' Mode: IX SPID:58 ECID:0 Ec:(0x78181580)
>> Value:0x57f04c80 Cost:(0/1ED4)
>> Victim Resource Owner:
>> ResType:LockOwner Stype:'OR' Mode: S SPID:53 ECID:0 Ec:(0x576E3580)
>> Value:0x6847aac0 Cost:(0/0)
>|||Kalen Delaney wrote:
> There is no application to do the parsing, afaik.
> Look up "Troubleshooting Deadlocks" in the Books Online. It goods a pretty
> good description of how to interpret the information
I understand how to interpret them, however, it is a pain. I thought by
now someone had enough of it and wrote something up. Sounds like a
weekend project.
Deadlocks in the error log
It seems that the information written to the error log about deadlocks
changed in 2005 and I can no longer tell what the numbers mean. Like
for instance, the information after KEY? I can't seem to find sql
server 2005 documentation on this. Can anyone point me to it?
Node:1
KEY: 8:72057594060537856 (9a03c330cb9d) CleanCnt:4 Mode:S Flags: 0x0
Wait List:
Owner:0x000000016A300880 Mode: X Flg:0x2 Ref:1 Life:02000000
SPID:90 ECID:0 XactLockInfo: 0x00000000C69213F8
SPID: 90 ECID: 0 Statement Type: UPDATE Line #: 805
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1535500699]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x000000015E8F5AD0 Mode: S SPID:91
BatchID:0 ECID:0 TaskProxy0x0000000169426598) Value:0x8011fbc0 Cost5/0)
NULL
Node:2
KEY: 8:72057594060537856 (9a03c330cb9d) CleanCnt:4 Mode:S Flags: 0x0
Grant List 0:
Owner:0x00000000851FAF80 Mode: S Flg:0x0 Ref:0 Life:00000001
SPID:84 ECID:0 XactLockInfo: 0x00000000D431A3A8
SPID: 84 ECID: 0 Statement Type: INSERT Line #: 424
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1052739003]
Grant List 3:
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x00000000C69213C0 Mode: X SPID:90
BatchID:0 ECID:0 TaskProxy0x00000000BE4D8598) Value:0x6a300880
Cost5/8728)
NULL
Node:3
KEY: 8:72057594059882496 (b000142fd0ae) CleanCnt:3 Mode:X Flags: 0x0
Wait List:
Owner:0x0000000100247C00 Mode: S Flg:0x2 Ref:1 Life:00000000
SPID:89 ECID:0 XactLockInfo: 0x0000000123AE8738
SPID: 89 ECID: 0 Statement Type: INSERT Line #: 424
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1052739003]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x00000000D431A370 Mode: S SPID:84
BatchID:0 ECID:0 TaskProxy0x00000000B7D8C598) Value:0x2a74e200 Cost5/0)
NULL
Node:4
KEY: 8:72057594059882496 (b000142fd0ae) CleanCnt:3 Mode:X Flags: 0x0
Grant List 1:
Owner:0x00000000801A62C0 Mode: X Flg:0x0 Ref:0 Life:02000000
SPID:90 ECID:0 XactLockInfo: 0x00000000C69213F8
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x0000000123AE8700 Mode: S SPID:89
BatchID:0 ECID:0 TaskProxy0x00000000AAE48598) Value:0x247c00 Cost5/0)
NULL
Victim Resource Owner:
ResType:LockOwner Stype:'OR'Xdes:0x0000000123AE8700 Mode: S SPID:89
BatchID:0 ECID:0 TaskProxy0x00000000AAE48598) Value:0x247c00 Cost5/0)
Deadlock encountered ... Printing deadlock information
Wait-for graph
NULLHi, Frank,
Thanks for your post.
From your description, I understand that you would like to know what the
KEY means in SQL error logs.
If I have misunderstood, please let me know.
KEY Identifies the key range within an index on which a lock is held or
requested. KEY is represented as KEY: db_id:hobt_id (index key hash value).
For example, KEY: 6:72057594057457664 (350007a4d329).
For more information, you can refer to:
Detecting and Ending Deadlocks
http://msdn2.microsoft.com/en-us/library/ms178104.aspx
If you have any other questions or concerns, please feel free to let me
know.
Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============
changed in 2005 and I can no longer tell what the numbers mean. Like
for instance, the information after KEY? I can't seem to find sql
server 2005 documentation on this. Can anyone point me to it?
Node:1
KEY: 8:72057594060537856 (9a03c330cb9d) CleanCnt:4 Mode:S Flags: 0x0
Wait List:
Owner:0x000000016A300880 Mode: X Flg:0x2 Ref:1 Life:02000000
SPID:90 ECID:0 XactLockInfo: 0x00000000C69213F8
SPID: 90 ECID: 0 Statement Type: UPDATE Line #: 805
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1535500699]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x000000015E8F5AD0 Mode: S SPID:91
BatchID:0 ECID:0 TaskProxy
0x0000000169426598) Value:0x8011fbc0 Cost5/0)NULL
Node:2
KEY: 8:72057594060537856 (9a03c330cb9d) CleanCnt:4 Mode:S Flags: 0x0
Grant List 0:
Owner:0x00000000851FAF80 Mode: S Flg:0x0 Ref:0 Life:00000001
SPID:84 ECID:0 XactLockInfo: 0x00000000D431A3A8
SPID: 84 ECID: 0 Statement Type: INSERT Line #: 424
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1052739003]
Grant List 3:
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x00000000C69213C0 Mode: X SPID:90
BatchID:0 ECID:0 TaskProxy
0x00000000BE4D8598) Value:0x6a300880Cost
5/8728)NULL
Node:3
KEY: 8:72057594059882496 (b000142fd0ae) CleanCnt:3 Mode:X Flags: 0x0
Wait List:
Owner:0x0000000100247C00 Mode: S Flg:0x2 Ref:1 Life:00000000
SPID:89 ECID:0 XactLockInfo: 0x0000000123AE8738
SPID: 89 ECID: 0 Statement Type: INSERT Line #: 424
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1052739003]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x00000000D431A370 Mode: S SPID:84
BatchID:0 ECID:0 TaskProxy
0x00000000B7D8C598) Value:0x2a74e200 Cost5/0)NULL
Node:4
KEY: 8:72057594059882496 (b000142fd0ae) CleanCnt:3 Mode:X Flags: 0x0
Grant List 1:
Owner:0x00000000801A62C0 Mode: X Flg:0x0 Ref:0 Life:02000000
SPID:90 ECID:0 XactLockInfo: 0x00000000C69213F8
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x0000000123AE8700 Mode: S SPID:89
BatchID:0 ECID:0 TaskProxy
0x00000000AAE48598) Value:0x247c00 Cost5/0)NULL
Victim Resource Owner:
ResType:LockOwner Stype:'OR'Xdes:0x0000000123AE8700 Mode: S SPID:89
BatchID:0 ECID:0 TaskProxy
0x00000000AAE48598) Value:0x247c00 Cost5/0)Deadlock encountered ... Printing deadlock information
Wait-for graph
NULLHi, Frank,
Thanks for your post.
From your description, I understand that you would like to know what the
KEY means in SQL error logs.
If I have misunderstood, please let me know.
KEY Identifies the key range within an index on which a lock is held or
requested. KEY is represented as KEY: db_id:hobt_id (index key hash value).
For example, KEY: 6:72057594057457664 (350007a4d329).
For more information, you can refer to:
Detecting and Ending Deadlocks
http://msdn2.microsoft.com/en-us/library/ms178104.aspx
If you have any other questions or concerns, please feel free to let me
know.
Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============
Deadlocks in the error log
It seems that the information written to the error log about deadlocks
changed in 2005 and I can no longer tell what the numbers mean. Like
for instance, the information after KEY? I can't seem to find sql
server 2005 documentation on this. Can anyone point me to it?
Node:1
KEY: 8:72057594060537856 (9a03c330cb9d) CleanCnt:4 Mode:S Flags: 0x0
Wait List:
Owner:0x000000016A300880 Mode: X Flg:0x2 Ref:1 Life:02000000
SPID:90 ECID:0 XactLockInfo: 0x00000000C69213F8
SPID: 90 ECID: 0 Statement Type: UPDATE Line #: 805
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1535500699]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x000000015E8F5AD0 Mode: S SPID:91
BatchID:0 ECID:0 TaskProxy0x0000000169426598) Value:0x8011fbc0 Cost5/0)
NULL
Node:2
KEY: 8:72057594060537856 (9a03c330cb9d) CleanCnt:4 Mode:S Flags: 0x0
Grant List 0:
Owner:0x00000000851FAF80 Mode: S Flg:0x0 Ref:0 Life:00000001
SPID:84 ECID:0 XactLockInfo: 0x00000000D431A3A8
SPID: 84 ECID: 0 Statement Type: INSERT Line #: 424
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1052739003]
Grant List 3:
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x00000000C69213C0 Mode: X SPID:90
BatchID:0 ECID:0 TaskProxy0x00000000BE4D8598) Value:0x6a300880
Cost5/8728)
NULL
Node:3
KEY: 8:72057594059882496 (b000142fd0ae) CleanCnt:3 Mode:X Flags: 0x0
Wait List:
Owner:0x0000000100247C00 Mode: S Flg:0x2 Ref:1 Life:00000000
SPID:89 ECID:0 XactLockInfo: 0x0000000123AE8738
SPID: 89 ECID: 0 Statement Type: INSERT Line #: 424
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1052739003]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x00000000D431A370 Mode: S SPID:84
BatchID:0 ECID:0 TaskProxy0x00000000B7D8C598) Value:0x2a74e200 Cost5/0)
NULL
Node:4
KEY: 8:72057594059882496 (b000142fd0ae) CleanCnt:3 Mode:X Flags: 0x0
Grant List 1:
Owner:0x00000000801A62C0 Mode: X Flg:0x0 Ref:0 Life:02000000
SPID:90 ECID:0 XactLockInfo: 0x00000000C69213F8
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x0000000123AE8700 Mode: S SPID:89
BatchID:0 ECID:0 TaskProxy0x00000000AAE48598) Value:0x247c00 Cost5/0)
NULL
Victim Resource Owner:
ResType:LockOwner Stype:'OR'Xdes:0x0000000123AE8700 Mode: S SPID:89
BatchID:0 ECID:0 TaskProxy0x00000000AAE48598) Value:0x247c00 Cost5/0)
Deadlock encountered ... Printing deadlock information
Wait-for graph
NULL
Hi, Frank,
Thanks for your post.
From your description, I understand that you would like to know what the
KEY means in SQL error logs.
If I have misunderstood, please let me know.
KEY Identifies the key range within an index on which a lock is held or
requested. KEY is represented as KEY: db_id:hobt_id (index key hash value).
For example, KEY: 6:72057594057457664 (350007a4d329).
For more information, you can refer to:
Detecting and Ending Deadlocks
http://msdn2.microsoft.com/en-us/library/ms178104.aspx
If you have any other questions or concerns, please feel free to let me
know.
Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
changed in 2005 and I can no longer tell what the numbers mean. Like
for instance, the information after KEY? I can't seem to find sql
server 2005 documentation on this. Can anyone point me to it?
Node:1
KEY: 8:72057594060537856 (9a03c330cb9d) CleanCnt:4 Mode:S Flags: 0x0
Wait List:
Owner:0x000000016A300880 Mode: X Flg:0x2 Ref:1 Life:02000000
SPID:90 ECID:0 XactLockInfo: 0x00000000C69213F8
SPID: 90 ECID: 0 Statement Type: UPDATE Line #: 805
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1535500699]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x000000015E8F5AD0 Mode: S SPID:91
BatchID:0 ECID:0 TaskProxy
0x0000000169426598) Value:0x8011fbc0 Cost5/0)NULL
Node:2
KEY: 8:72057594060537856 (9a03c330cb9d) CleanCnt:4 Mode:S Flags: 0x0
Grant List 0:
Owner:0x00000000851FAF80 Mode: S Flg:0x0 Ref:0 Life:00000001
SPID:84 ECID:0 XactLockInfo: 0x00000000D431A3A8
SPID: 84 ECID: 0 Statement Type: INSERT Line #: 424
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1052739003]
Grant List 3:
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x00000000C69213C0 Mode: X SPID:90
BatchID:0 ECID:0 TaskProxy
0x00000000BE4D8598) Value:0x6a300880Cost
5/8728)NULL
Node:3
KEY: 8:72057594059882496 (b000142fd0ae) CleanCnt:3 Mode:X Flags: 0x0
Wait List:
Owner:0x0000000100247C00 Mode: S Flg:0x2 Ref:1 Life:00000000
SPID:89 ECID:0 XactLockInfo: 0x0000000123AE8738
SPID: 89 ECID: 0 Statement Type: INSERT Line #: 424
Input Buf: RPC Event: Proc [Database Id = 8 Object Id = 1052739003]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x00000000D431A370 Mode: S SPID:84
BatchID:0 ECID:0 TaskProxy
0x00000000B7D8C598) Value:0x2a74e200 Cost5/0)NULL
Node:4
KEY: 8:72057594059882496 (b000142fd0ae) CleanCnt:3 Mode:X Flags: 0x0
Grant List 1:
Owner:0x00000000801A62C0 Mode: X Flg:0x0 Ref:0 Life:02000000
SPID:90 ECID:0 XactLockInfo: 0x00000000C69213F8
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x0000000123AE8700 Mode: S SPID:89
BatchID:0 ECID:0 TaskProxy
0x00000000AAE48598) Value:0x247c00 Cost5/0)NULL
Victim Resource Owner:
ResType:LockOwner Stype:'OR'Xdes:0x0000000123AE8700 Mode: S SPID:89
BatchID:0 ECID:0 TaskProxy
0x00000000AAE48598) Value:0x247c00 Cost5/0)Deadlock encountered ... Printing deadlock information
Wait-for graph
NULL
Hi, Frank,
Thanks for your post.
From your description, I understand that you would like to know what the
KEY means in SQL error logs.
If I have misunderstood, please let me know.
KEY Identifies the key range within an index on which a lock is held or
requested. KEY is represented as KEY: db_id:hobt_id (index key hash value).
For example, KEY: 6:72057594057457664 (350007a4d329).
For more information, you can refer to:
Detecting and Ending Deadlocks
http://msdn2.microsoft.com/en-us/library/ms178104.aspx
If you have any other questions or concerns, please feel free to let me
know.
Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
Subscribe to:
Posts (Atom)