October 8, 2010 at 5:34 pm
I'm seeing tons of entries in the SQL Server Log that I can't explain or understand. Each has a system spid identified by something like spid51s. The entries are all over the board. I've included quite a few below. Does anyone know where they could be coming from, or how I could figure that out? For instance, I saw the following entry but found nothing on google for machineapplicationmap. I also couldn't turn anything up in any of the sys.objects tables.
update machineapplicationmap set enabled = 0 from applicationlist where applicationlist.appid = machineapplicationmap.appid and appgroupid<>2 and machineid=15
Here are some others:
1:51:24 spid23s PMwaiter-list
1:51:24 spid23s PMowner id=processb84f28 mode=X
1:51:24 spid23s PMowner-list
1:51:24 spid23s PMridlock fileid=3 pageid=372759 dbid=7 objectname=[dbname].dbo.MachineApplicationMap id=lockf58e340 mode=X associatedObjectId=42355481772032
1:51:24 spid23s PMresource-list
1:51:24 spid23s PMupdate machineapplicationmap set enabled = 0 from applicationlist where applicationlist.appid =
PMmachineapplicationmap.appid and appgroupid<>2 and machineid=15
1:51:24 spid23s PMinputbuf
This group all has the same SPID and was logged at the same time. I'm stumped.
Thanks!
October 9, 2010 at 2:12 am
Got any traceflags on? If so, which ones?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 11, 2010 at 9:06 am
Hi Gail,
Thanks for the response, I didn't think of traceflags. I ran DBCC TRACESTATUS and got the following two results:
TraceFlag Status Global Session
1204 1 1 0
1222 1 1 0
Using event notifications that were already setup and logging on this server, I do see deadlocks. The following is a portion of the deadlock graph:
<process-list>
<process id="process84a898" taskpriority="0" logused="84" waitresource="RID: 7:4:92768:119" waittime="406" ownerId="1438083206" transactionname="UPDATE" lasttranstarted="2010-10-11T08:23:43.957" XDES="0xee39770" lockMode="U" schedulerid="1" kpid="1004" status="suspended" spid="107" sbid="0" ecid="0" priority="0" transcount="2" lastbatchstarted="2010-10-11T08:23:43.957" lastbatchcompleted="2010-10-11T08:23:43.957" clientapp=".Net SqlClient Data Provider" hostname="host1" hostpid="1280" loginname="<loginname>" isolationlevel="read committed (2)" xactid="1438083206" currentdb="7" lockTimeout="4294967295" clientoption1="671088672" clientoption2="128056">
<executionStack>
<frame procname="adhoc" line="1" sqlhandle="0x020000002195ee30b3177ba863af305d540c8a5ba7d3f688">
update machineapplicationmap set enabled = 1 from applicationlist where applicationlist.appid = machineapplicationmap.appid and appgroupid=3 and machineid=20 </frame>
</executionStack>
<inputbuf>
update machineapplicationmap set enabled = 1 from applicationlist where applicationlist.appid = machineapplicationmap.appid and appgroupid=3 and machineid=20 </inputbuf>
</process>
<process id="process8d8b68" taskpriority="0" logused="84" waitresource="RID: 7:4:84018:90" waittime="109" ownerId="1438083286" transactionname="UPDATE" lasttranstarted="2010-10-11T08:23:43.977" XDES="0x32d8e250" lockMode="U" schedulerid="2" kpid="764" status="suspended" spid="244" sbid="0" ecid="0" priority="0" transcount="2" lastbatchstarted="2010-10-11T08:23:43.977" lastbatchcompleted="2010-10-11T08:23:43.977" clientapp=".Net SqlClient Data Provider" hostname="host2" hostpid="1240" loginname="<loginname>" isolationlevel="read committed (2)" xactid="1438083286" currentdb="7" lockTimeout="4294967295" clientoption1="671088672" clientoption2="128056">
<executionStack>
<frame procname="adhoc" line="1" sqlhandle="0x02000000c09ea71c16aaeb333c0cb23e86e01fce83dce141">
update machineapplicationmap set enabled = 1 from applicationlist where applicationlist.appid = machineapplicationmap.appid and appgroupid=3 and machineid=12 </frame>
</executionStack>
<inputbuf>
update machineapplicationmap set enabled = 1 from applicationlist where applicationlist.appid = machineapplicationmap.appid and appgroupid=3 and machineid=12 </inputbuf>
</process>
</process-list>
Looks like the it's the deadlock graph output that is being written to the log, thanks again Gail!
October 11, 2010 at 10:07 am
Turn 1204 off. It's the old deadlock detection traceflag. The info provided by 1222 (also deadlock detection and new from SQL 2005) is far more detailed and far superior
Flag may be in the server's startup parameters or a startup procedure.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply