Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
lleemon
Starting Member
24 Posts |
 Posted - 2007-09-04 : 15:30:04
|
| We have a process that we can't stop. if we do a kill <spid> WITH STATUSONLY it says we have 0 left but the cpu field keeps climbing.If we do a Kill <spid> is there any chance it could corrupt the rest of the databases we have on that sql server?We did a DBCC INPUTBUFFER (spid) and it returned create unique index p_key on <db>.dbo.<table>(<field>)Is turning off sql server the only option? |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2007-09-04 : 15:33:06
|
| do a backup if possible (and if you're too afraid of the consequence).. and kill the spidkilling the spid is better than aborting sql serviceI'm not a guru but that's how I'll do it.--------------------keeping it simple... |
 |
|
|
lleemon
Starting Member
24 Posts |
Posted - 2007-09-04 : 15:38:28
|
| what if 'KILL <spid>' doesn't do anything? Any other options? |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2007-09-04 : 15:42:08
|
| didn't it do anything?if it doesn't do it, you can always trace where the spid is coming from, ask the person to nicely disconnect and you're set...if you did it... disconnect...if you don't know where it's coming from, just kill the spid...if you don't want to... disconnect the network cableif it doesn't work...shut the service down--------------------keeping it simple... |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-09-04 : 23:20:51
|
| Sql will do rollback once you killed the process, it takes time. |
|
|
|
|
|
|
Kill row in sysprocesses