How do I kill a restore?

Question: I have a few databases that were told to restore via a
script. They've been stuck in a 'Restoring...' state for two days now,
and I need to kill it.
What can I do from administration standpoint to stop this?
Thanks,
MichaelThe restore process is probably done by now, and the databases are left in t
he restoring state
(either because the restore process was terminated, or because you restore u
sing the NORECOVERY
option). If it is the later, try:
RESTORE DATABASE dbname WITH RECOVERY
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Michael Gorsuch" <michael.gorsuch@.gmail.com> wrote in message
news:1162563793.422412.281130@.m73g2000cwd.googlegroups.com...
> Question: I have a few databases that were told to restore via a
> script. They've been stuck in a 'Restoring...' state for two days now,
> and I need to kill it.
> What can I do from administration standpoint to stop this?
> Thanks,
> Michael
>|||I believe it is the former - when I try and run "RESTORE DATABASE
trial75441 WITH RECOVERY", I receive the following:
Msg 4319, Level 16, State 3, Line 1
A previous restore operation was interrupted and did not complete
processing on file 'trial75441_log'. Either restore the backup set that
was interrupted or restart the restore sequence.
Is there a way to force this restore to terminate via a command? If
not, what command allows me to restart?
Again, I apologize for my ignorance. I've away from the Windows
sysadmin side for a couple of years, and am now getting back into it
heavily. By the way, is there a good book that you can recommend for
running SQL Server 2005?
On Nov 3, 9:58 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> The restore process is probably done by now, and the databases are left in
the restoring state
> (either because the restore process was terminated, or because you restore
using the NORECOVERY
> option). If it is the later, try:
> RESTORE DATABASE dbname WITH RECOVERY
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://www.solidqualitylearning.com/
> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in messagenews:1162563
793.422412.281130@.m73g2000cwd.googlegroups.com...
>
>
>
>|||Since the RESTORE process creates the database for you, the easiest way is p
robably to just DROP
DATABASE and then start the restore operation from scratch.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Michael Gorsuch" <michael.gorsuch@.gmail.com> wrote in message
news:1162567958.824002.311440@.k70g2000cwa.googlegroups.com...
>I believe it is the former - when I try and run "RESTORE DATABASE
> trial75441 WITH RECOVERY", I receive the following:
> Msg 4319, Level 16, State 3, Line 1
> A previous restore operation was interrupted and did not complete
> processing on file 'trial75441_log'. Either restore the backup set that
> was interrupted or restart the restore sequence.
> Is there a way to force this restore to terminate via a command? If
> not, what command allows me to restart?
> Again, I apologize for my ignorance. I've away from the Windows
> sysadmin side for a couple of years, and am now getting back into it
> heavily. By the way, is there a good book that you can recommend for
> running SQL Server 2005?
> On Nov 3, 9:58 am, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>|||I just had the same problem and doing what Tibor Karaszi mentioned
worked.
I dropped the databases that were created by the failed restore and
re-ran the restore script and it worked the 2nd time around.
Tibor Karaszi wrote:[vbcol=seagreen]
> Since the RESTORE process creates the database for you, the easiest way is
probably to just DROP
> DATABASE and then start the restore operation from scratch.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Michael Gorsuch" <michael.gorsuch@.gmail.com> wrote in message
> news:1162567958.824002.311440@.k70g2000cwa.googlegroups.com...|||Perfect guys. I did that, and I'm in good shape.
Thank you all for your help.
On Nov 3, 11:38 am, "Hulicat" <dennis_A_wh...@.yahoo.com> wrote:[vbcol=seagreen]
> I just had the same problem and doing what Tibor Karaszi mentioned
> worked.
> I dropped the databases that were created by the failed restore and
> re-ran the restore script and it worked the 2nd time around.
> Tibor Karaszi wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>