August 14, 2013 at 12:40 am
Hi All,
Today I got a request to kill SSIS process which SID is XXX.
After killing my process in SQL erver its showing hung stage(Killed/Rollback) from 2hours. When i tryed to kill the process from Windows its showing 2 process with same name. Please let us know how to identify which process need to be kill.
Please reply ASAP
August 14, 2013 at 1:11 am
Do both of the processes have the same number as well? If so, it's the same process, probably showing up twice due to parallelism. If it has a state of KILLED/ROLLBACK then you'll need to sit and wait for it to roll back. Is it doing any harm?
Please reply ASAP
We're all volunteers here, and we have our own jobs to do. Having something done to your own timescale usually involves paying for it.
John
August 14, 2013 at 1:33 am
Thanks for reply. I killed from SQL server. My command execute successfully but when i did
select * from sys.sysprocesses where sid = 100
still that session was present and its showing state of KILLED/ROLLBACK from 2 hors
Then i thought to kill from windows - TaskManager - Processes - Checked marked on "Show process from all users.
Then i seen 2 SSIS process has running. Because in Windows i Cant see SID.I am confuse which one to kill.
Reply - ASAP
August 14, 2013 at 1:38 am
Jon,
Its not giving any thing harm but I m getting request from User to kill the process.
August 14, 2013 at 1:40 am
You're the DBA. Just say no if the request isn't appropriate.
John
August 14, 2013 at 1:44 am
John,
I am DBA, except me only primary DBA can kill this. I told that user i m getting confuse so can you wait some time. He told ok for this. But i want to know the solution.
August 14, 2013 at 1:48 am
The solution is to wait. The transaction has to be rolled back in order to leave your database in a transactionally consistent state. This can take time depending, amongst other things, on the complexity of the transaction.
John
August 14, 2013 at 1:54 am
Het john.. Thank you very much but here i have one more thing to ask.. Now my user tolt it is ok.. but If he will say you have to kill... so is any way is there so i can kill this... As per my knowlege i know i can do from Task manager but some other options
August 14, 2013 at 1:58 am
You have killed it. Now you just have to wait for it to die. If you try to kill it through Windows, you have two options:
(1) Kill the sqlserver process. I hope I don't have to explain why that is a very bad idea.
(2) Kill the process that spawned the connection to SQL Server. But if you do that you will still have to wait for the transaction to roll back.
John
August 14, 2013 at 2:31 am
Hi rajesh ,
wait for rollback completion because from how long time that spid is using that much time will take for rollback action.
Thanks,
subahan.
August 14, 2013 at 2:55 am
Hi subahan,
Still is in same conditions. user told that if will face some blocking issue u have to resolve it. So I m finding the solution If problem will come what action i have to take care
August 14, 2013 at 2:58 am
Hi subahan - Now there is no blocking but user has told if blocking isssue will come you have to resolved. So i am finding the solution if blocking will come .. what action i have to take.
August 14, 2013 at 3:33 am
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply