This is sad, answering my own question, but for everyone else:
The TLINK utlitity will allow you to associate an MTS package to an mtx.exe PID.
In SQL Server, put the context id or activity id of the component in the application name of the connection. This way it will show up in current activity or sp_who.
Thanks for your question!But i donnot know why you need to know the SPID in SQL server.The impersonaton is not a recommended way to connect to SQL server,so the SPID is not important for SQL server.
BTW.. it's TLIST, not TLINK as I typo'ed earlier...
If a hung component causes resources on SQL Server to be hung on sql server (causing blocked transactions or deadlocks), then it would be a good thing to be able to drill down to the problem to fix it if you can associate a component to a SPID...
I have a memory leak that I suspect is caused by a component running under MTS. Sqlsevr.exe seems to slowly climb in consumption of virtual memory until it is exhausted. There is an Mtx.exe process running constantly under one single PID. I would like to be able to link this instance of mtx.exe with the MTS package to start troubleshooting. I have tried TLINK.EXE, but the associated process name is simply given as OLEChannelWnd for all mtx.exe processes on the server. You mention that you can link the PID to an MTS package. How can I do this?
Thanks.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.