''Tas Manager'' and ''signal handler'', what to do about them?
-
Hi there,
Running a IntegrityCheck process this ends with an error: database(master) cannot be set in single_user mode. So I check things and se only several processesin the background with the CMD TASK MANAGER or SIGNAL HANDLER. Login time and last batch time are weeks in the past, probably the start-up or re-boot of this server. Processe are not waiting, but their status is still BACKGROUND. Asking the properties don't show anything.
As far as I can tell there are no other apls outside SQL Server interacting with the database at the time of the IntegrityCheck. two questions:
Can it be, that these background processes prevent to set the dab to SINGLE_USER?
What are these processes doing? I try to imagine what it means, having 'Task Manager' in the CMD column: is the TM interacting with SQL Server? How & why, if so? Killing a TM process should be possible, but it is not.
Well, third question: are there other possible causes to prevent the use of SINGLE_USER on a db?
Greetz,
Hans Brouwer -
If you uncheck the 'attempt to repair problems' item on your Integrity Checks job, the message will disappear. Using this option that attempts to place the DB in single user mode.
As to your other questions what are the results of sp_who2? This should show details on any active connections and you can investigate from there.
Hope this helps.
My hovercraft is full of eels.
-
I believe master can only be put into single user mode with the startup parameter.
-
Tnx for the response.
On the master db: maybe you are right. However, the problem occurs with user-databases as well. On unchecking the auto-repair option: I am aware that this will stop generating this message. But this does not really answer my question. Why NOY use this option? Well, obviously because I don't want these errors, so I have turned off this feature. I realy would like to use it and I am trying to find out how to prevent this situation.
It is not an urgent matter, but I am still wondering what 'Task Manager' in the CMD column means...
Tnx anyway.
Greetz,
Hans Brouwer -
It is not an urgent matter, but I am still wondering what 'Task Manager' in the CMD column means...
I can not give a complete answer to that, but it definitely does not have anything to do with the Windows Task Manager application. The processes with spids from 1-50 are all internally used, and my guess is that TASK MANAGER indicates that the process is associated with handling tasks handed to the scheduler in SQL Server. You should not (and I think can not?) kill these internally used processes.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply