SQL Server 2005 Backup Running

[katekis]

I am a new SQL Server 2005 DBA and needs some help on killing a backup.

I had a backup job fail over the weekend, the backup normally takes less then 5 minutes to run on the weekend so thought no big deal to run it now. I started the backup about an hour ago and it is still running. I probably should not have started the backup during the mid day and want to kill the backup.

I have never killed a job before so wanted to be sure I am doing the right thing to stop this backup job?

The backup is not running under my ID so I believe I can kill it. I have the SPID, is this the correct command I enter to kill a backup job?

sp_who

Kill 58

(58 is my SPID I got when I did sp_who)

Any advice before I kill the job, I am new and do want to screwup? I have never killed a job before.

 

[katekis]

I did not kill the backup yet because it does not seem to be causing a problem with slowness, not too many other users are currently using this database. If I need to eventually kill the job do I have the commands correct? Is there any other precautions I should take before killing a backup?

 

[JayKusch]

Yes ... your KILL command should do the trick.

But backups on the server and DB "should" not cause too much of a performance issue (though in a few very rare cases I have seen the backups being the culprit).

One issue you have to be aware of is disc space as the backup spools to disc.

Thanks

J. Kusch