'Database Loading' state after Restore

Hi,
I have a Windows Server 2003 cluster setup with 3 SQL
Server 2000 virtual servers installed. When I perform a
restore of an 85 GB database, the database gets stuck in
a 'Database Loading' state. It doesn't appear to be a
resource issue since SQL has access to all 8 processors
and 4 GB of memory and the system is not under stress. I
have checked the SQL and Event Viewer logs for clues but
have found nothing to pursue. Any assistance is greatly
appreciated.
Sincerely,
ABGABG,
Did you get a message that the database restore finished
successfully (even though it is 'loading' state')?
During the restore process, you must the with 'RECOVERY'
OPTION.
If the restore is finished, you could do the following to
recover the database:
RESTORE DATABASE_NAME
WITH RECOVERY
hth
DeeJay
>--Original Message--
>Hi,
> I have a Windows Server 2003 cluster setup with 3 SQL
>Server 2000 virtual servers installed. When I perform a
>restore of an 85 GB database, the database gets stuck in
>a 'Database Loading' state. It doesn't appear to be a
>resource issue since SQL has access to all 8 processors
>and 4 GB of memory and the system is not under stress. I
>have checked the SQL and Event Viewer logs for clues but
>have found nothing to pursue. Any assistance is greatly
>appreciated.
> Sincerely,
> ABG
>.
>|||Yes, it stated that the recovery completed. Although the
database stayed in Loading state. I'm running the restore
from Enterprise Manager, is there a way to specify
the 'Recovery' option from here? Or must the restore be
performed from Query Analyzer? Thank you for your reply.
Sincerely,
ABG
>--Original Message--
>ABG,
>Did you get a message that the database restore finished
>successfully (even though it is 'loading' state')?
>During the restore process, you must the with 'RECOVERY'
>OPTION.
>If the restore is finished, you could do the following to
>recover the database:
>RESTORE DATABASE_NAME
>WITH RECOVERY
>hth
>DeeJay
>>--Original Message--
>>Hi,
>> I have a Windows Server 2003 cluster setup with 3 SQL
>>Server 2000 virtual servers installed. When I perform a
>>restore of an 85 GB database, the database gets stuck in
>>a 'Database Loading' state. It doesn't appear to be a
>>resource issue since SQL has access to all 8 processors
>>and 4 GB of memory and the system is not under stress. I
>>have checked the SQL and Event Viewer logs for clues but
>>have found nothing to pursue. Any assistance is greatly
>>appreciated.
>> Sincerely,
>> ABG
>>.
>.
>|||In EM, right.most tab (at the bottom), you have option for
RECOVERY/NORECOVERY/STANDBY. Default is, however RECOVERY on the last backup
(the topmost alternative). The command shown by DeeJay to recovery without
doing an actual restore is not available from EM.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"ABG" <anonymous@.discussions.microsoft.com> wrote in message
news:03c101c3a8a0$d4e30f70$a401280a@.phx.gbl...
> Yes, it stated that the recovery completed. Although the
> database stayed in Loading state. I'm running the restore
> from Enterprise Manager, is there a way to specify
> the 'Recovery' option from here? Or must the restore be
> performed from Query Analyzer? Thank you for your reply.
> Sincerely,
> ABG
> >--Original Message--
> >ABG,
> >
> >Did you get a message that the database restore finished
> >successfully (even though it is 'loading' state')?
> >
> >During the restore process, you must the with 'RECOVERY'
> >OPTION.
> >
> >If the restore is finished, you could do the following to
> >recover the database:
> >
> >RESTORE DATABASE_NAME
> >WITH RECOVERY
> >
> >hth
> >
> >DeeJay
> >>--Original Message--
> >>Hi,
> >> I have a Windows Server 2003 cluster setup with 3 SQL
> >>Server 2000 virtual servers installed. When I perform a
> >>restore of an 85 GB database, the database gets stuck in
> >>a 'Database Loading' state. It doesn't appear to be a
> >>resource issue since SQL has access to all 8 processors
> >>and 4 GB of memory and the system is not under stress. I
> >>have checked the SQL and Event Viewer logs for clues but
> >>have found nothing to pursue. Any assistance is greatly
> >>appreciated.
> >> Sincerely,
> >> ABG
> >>
> >>.
> >>
> >.
> >