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:
>
>
>
>
>
>
>
>
>
>
>
>
>
Showing posts with label via. Show all posts
Showing posts with label via. Show all posts
Monday, March 26, 2012
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,
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.asphttp://www.solidqualitylearning.com/
> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in messagenews:1162563793.422412.281130@.m73g2000cwd.g ooglegroups.com...
>
>
|||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.googlegr oups.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:
>
>
>
>
>
>
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.asphttp://www.solidqualitylearning.com/
> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in messagenews:1162563793.422412.281130@.m73g2000cwd.g ooglegroups.com...
>
>
|||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.googlegr oups.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:
>
>
>
>
>
>
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 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 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:
> 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.asphttp://www.solidqualitylearning.com/
> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in messagenews: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|||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...
>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:
>> 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.asphttp://www.solidqualitylearning.com/
>> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in
>> messagenews: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 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:
> 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...
> >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:
> >> 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.asphttp://www.solidqualitylearning.com/
> >>
> >> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in
> >> messagenews: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
> >|||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:
> 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:
> > 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.gors...@.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:
> > >> 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.asphttp://www.solidqualityle...
> > >> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in
> > >> messagenews: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,
> > >> > Michaelsql
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 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 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:
> 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.asphttp://www.solidqualitylearning.com/
> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in messagenews: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|||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...
>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:
>> 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.asphttp://www.solidqualitylearning.com/
>> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in
>> messagenews: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 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:
> 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...
> >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:
> >> 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.asphttp://www.solidqualitylearning.com/
> >>
> >> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in
> >> messagenews: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
> >|||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:
> 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:
> > 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.gors...@.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:
> > >> 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.asphttp://www.solidqualityle...
> > >> "Michael Gorsuch" <michael.gors...@.gmail.com> wrote in
> > >> messagenews: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,
> > >> > Michaelsql
Wednesday, March 21, 2012
How do I Hide Databases from External Users?
I am going to give user rights for an external user to connect to my SQL Server via Client Network Utility.
Atlough I have given user permissions to only access one database and not the whole list, how do I make sure that they cannot see all the other databases on my SQL Server?
I have 20 instances of databases on my SQL Server and ideally I would like to give 20 different people access - but each of them when they enter my SQL Server, should not even know that the other databases exist.
Thanks.RE:
Q1 I am going to give user rights for an external user to connect to my SQL Server via Client Network Utility.
Q2 Although I have given user permissions to only access one database and not the whole list, how do I make sure that they cannot see all the other databases on my SQL Server?
I have 20 instances of databases on my SQL Server and ideally I would like to give 20 different people access -
Q3 but each of them when they enter my SQL Server, should not even know that the other databases exist. Thanks.
A1 {What was meant is not 100% clear; however, bestowing "[user rights for an external user to connect to SQL Server]" would generally be accomplished within Enterprise Manager, *Query Analyser, osql, isql, or programmatically, i.e.(via an API: ADO, CLib, DMO, OLEDB, etc.,); but not via the Client Network Utility (at least not directly)?}
A2 One may meet such requirements by designing the user application(s), i.e.(the ones the users will use with their respective DBs), such that other DB catalogs are not displayed. (This is arguably probably one of the better means of meeting such a requirement.)
Note: Various "all encompassing" implementation approaches may entail significant negative consequences. For example this includes many implementations that:
a Deny users Select and Exec rights to certain objects in the Master DB.
b Modify / add objects to the Master DB (this option especially, is NOT recommended).
c Require special connectivity software that supports the desired feature set (custom made ODBC, Sql Server, OLEDB, etc., drivers).
A3 You may wish to verify that this is in fact an important requirement. (That is, one that is worth the ramifications of the means chosen to implement a design that will meet the requirement.) As noted in A2, maintainability and / or functionality may be impaired with some kinds of "DB hiding" implementation approaches.
--
* The following Special Stored Procedures are supported in MS Sql Server 2k (execute from QA, etc.) for managing security:
sp_addalias
sp_addapprole
sp_addgroup
sp_addlinkedsrvlogin
sp_addlogin
sp_addremotelogin
sp_addrole
sp_addrolemember
sp_addserver
sp_addsrvrolemember
sp_adduser
sp_approlepassword
sp_change_users_login
sp_changedbowner
sp_changegroup
sp_changeobjectowner
sp_dbfixedrolepermission
sp_defaultdb
sp_defaultlanguage
sp_denylogin
sp_dropalias
sp_dropapprole
sp_dropgroup
sp_droplinkedsrvlogin
sp_droplogin
sp_dropremotelogin
sp_droprole
sp_droprolemember
sp_dropserver
sp_dropsrvrolemember
sp_dropuser
sp_grantdbaccess
sp_grantlogin
sp_helpdbfixedrole
sp_helpgroup
sp_helplinkedsrvlogin
sp_helplogins
sp_helpntgroup
sp_helpremotelogin
sp_helprole
sp_helprolemember
sp_helprotect
sp_helpsrvrole
sp_helpsrvrolemember
sp_helpuser
sp_password
sp_remoteoption
sp_revokedbaccess
sp_revokelogin
sp_setapprole
sp_srvrolepermission
sp_validatelogins|||With what tools will your users be connecting to your Server? ODBC, OSQL, Enterprise Manager?|||Originally posted by Paul Young
With what tools will your users be connecting to your Server? ODBC, OSQL, Enterprise Manager?
Thank you for your posts :)
I am using EM to connect|||Great, what will your users use to connect?
If your users will use EM or Query Analyzer then they have enough to see the diffrent DBs with little to no effort. A knowlegable user can even see system tables via I/OSQL. Past that, in ODBC a use will still be able to get a list of DB's if they specify a database when setting up the DSN.sql
Atlough I have given user permissions to only access one database and not the whole list, how do I make sure that they cannot see all the other databases on my SQL Server?
I have 20 instances of databases on my SQL Server and ideally I would like to give 20 different people access - but each of them when they enter my SQL Server, should not even know that the other databases exist.
Thanks.RE:
Q1 I am going to give user rights for an external user to connect to my SQL Server via Client Network Utility.
Q2 Although I have given user permissions to only access one database and not the whole list, how do I make sure that they cannot see all the other databases on my SQL Server?
I have 20 instances of databases on my SQL Server and ideally I would like to give 20 different people access -
Q3 but each of them when they enter my SQL Server, should not even know that the other databases exist. Thanks.
A1 {What was meant is not 100% clear; however, bestowing "[user rights for an external user to connect to SQL Server]" would generally be accomplished within Enterprise Manager, *Query Analyser, osql, isql, or programmatically, i.e.(via an API: ADO, CLib, DMO, OLEDB, etc.,); but not via the Client Network Utility (at least not directly)?}
A2 One may meet such requirements by designing the user application(s), i.e.(the ones the users will use with their respective DBs), such that other DB catalogs are not displayed. (This is arguably probably one of the better means of meeting such a requirement.)
Note: Various "all encompassing" implementation approaches may entail significant negative consequences. For example this includes many implementations that:
a Deny users Select and Exec rights to certain objects in the Master DB.
b Modify / add objects to the Master DB (this option especially, is NOT recommended).
c Require special connectivity software that supports the desired feature set (custom made ODBC, Sql Server, OLEDB, etc., drivers).
A3 You may wish to verify that this is in fact an important requirement. (That is, one that is worth the ramifications of the means chosen to implement a design that will meet the requirement.) As noted in A2, maintainability and / or functionality may be impaired with some kinds of "DB hiding" implementation approaches.
--
* The following Special Stored Procedures are supported in MS Sql Server 2k (execute from QA, etc.) for managing security:
sp_addalias
sp_addapprole
sp_addgroup
sp_addlinkedsrvlogin
sp_addlogin
sp_addremotelogin
sp_addrole
sp_addrolemember
sp_addserver
sp_addsrvrolemember
sp_adduser
sp_approlepassword
sp_change_users_login
sp_changedbowner
sp_changegroup
sp_changeobjectowner
sp_dbfixedrolepermission
sp_defaultdb
sp_defaultlanguage
sp_denylogin
sp_dropalias
sp_dropapprole
sp_dropgroup
sp_droplinkedsrvlogin
sp_droplogin
sp_dropremotelogin
sp_droprole
sp_droprolemember
sp_dropserver
sp_dropsrvrolemember
sp_dropuser
sp_grantdbaccess
sp_grantlogin
sp_helpdbfixedrole
sp_helpgroup
sp_helplinkedsrvlogin
sp_helplogins
sp_helpntgroup
sp_helpremotelogin
sp_helprole
sp_helprolemember
sp_helprotect
sp_helpsrvrole
sp_helpsrvrolemember
sp_helpuser
sp_password
sp_remoteoption
sp_revokedbaccess
sp_revokelogin
sp_setapprole
sp_srvrolepermission
sp_validatelogins|||With what tools will your users be connecting to your Server? ODBC, OSQL, Enterprise Manager?|||Originally posted by Paul Young
With what tools will your users be connecting to your Server? ODBC, OSQL, Enterprise Manager?
Thank you for your posts :)
I am using EM to connect|||Great, what will your users use to connect?
If your users will use EM or Query Analyzer then they have enough to see the diffrent DBs with little to no effort. A knowlegable user can even see system tables via I/OSQL. Past that, in ODBC a use will still be able to get a list of DB's if they specify a database when setting up the DSN.sql
Subscribe to:
Posts (Atom)