June 30, 2004 at 11:25 am
I am experiencing problems with multiple 'phantom' sessions connecting to the master data base. These sessions come in as
SQLDMO1
SQLDMO2
SQLDMO3
and so on..
we don't believe this is related to any user activity
has anyone seen this before?
June 30, 2004 at 12:19 pm
I have seen this before but forget the exact details on other areas. However if someone builds and application using DMO to connect to the server and does set the app name it will show SQL DMO which is most likely your actuall occurance.
July 1, 2004 at 7:02 am
These 'phantom connections' typically are connections from a DTS package. In some cases they appear to remain connected for some time after the actual connection has completed its work. If you want or have to eliminate them, you can issue a kill command for that SPID, but they will timeout at some later point.
SQL DMO is an API that is used to manage SQL Server. The acronym stands for SQL Server Data Management Objects. Search in MSDN for more information.
July 1, 2004 at 11:00 am
I've used SQL DMO to control jobs from the ASP pages...Every time you would refresh a page a new instance of SQL DMO would appear in the process list. Eventually, they would time out and kill themselves.
July 1, 2004 at 5:01 pm
I've seen them as well, sometimes from jobs started under sql agent that got blocked - possibly maint plan steps, been a while since I noticed it.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply