November 11, 2002 at 3:23 pm
Question: A proccess hangs the MSSQL service. It restart, and then i can check which was the spid that produced the problem. How can i match that spid with a login?
November 11, 2002 at 3:36 pm
Once the condition is over you may not be able too. If the SPID was to an item that has not disconnected them sp_who or sp_who2 may help. If the item has disconnected and something else taken that position it will not be the same one. Best bet is to use SQL Profiler to catch the process and the User Account at the same time, plus you can get the originating host name.
November 11, 2002 at 4:18 pm
Not possible unless you have profiling setup
Simon Sabin
Co-author of SQL Server 2000 XML Distilled
http://www.amazon.co.uk/exec/obidos/ASIN/1904347088
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
November 12, 2002 at 9:21 am
Simon, what you mean? I'm logged as a SA...
quote:
Not possible unless you have profiling setupSimon Sabin
Co-author of SQL Server 2000 XML Distilled
http://www.amazon.co.uk/exec/obidos/ASIN/1904347088
November 12, 2002 at 9:28 am
He's saying that unless you have profiling set up to catch the login, you won't be able to accurrately map the spid back to the Login using it. Same as Antares...
and they are right.
November 12, 2002 at 9:42 am
If the service actually hangs, you can produce a user dump... harder to read and decipher, but doesn't require Profiler to be running. You can use AD+ in "hang" mode:
http://support.microsoft.com/default.aspx?scid=kb;en-us;286350
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply