June 3, 2006 at 7:44 am
We started a native SQL backup of two databases to an external hard drive via a scheduled job as a test of the external drive as a backup device. The backup was running very long as the databases being backed up were over 200GB. We cancelled the backup, but now the rollback of that process has been running over 20 hours and we need to continue with operations on the server.
Can we kill the SPID for the backup, and if we do so, what ramifications could we face by killing that process off by killing the SPID or rebooting the host? Will this cause database corruption?
June 5, 2006 at 10:17 am
I wouldn't think a backup would roll back as what could it roll back to ? - possibly the transaction log I suppose. You could try stopping and restarting the agent service, other than that you'll need to stop and restart the sql service. It shouldn't screw the database, but if you're worried you could try dettaching the database. If it detaches ok then you could reboot the server or whatever.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply