restore db stuck loading

Hi

I am trying to copy a 20 GB database from server 1 to 2. I took a full
backup, copied to server2 and restored ( ready for use) using EM.

After the message restore completed, I see the database's status as LOADING.
We are on Sql Server 2000 (8.00.818) on Windows 2000 Adv Servers.

I ran dbcc on the source DB and it returned no errors. I tried the command
'restore db with recovery ' which didnot help. I get an message saying that
the data file is only partially restored.. It seems the last resort is to
change the status in system tables.

Any ideas?

Thanks
Ragu(ragudba@.sbcglobal.net) writes:
> I am trying to copy a 20 GB database from server 1 to 2. I took a full
> backup, copied to server2 and restored ( ready for use) using EM.
> After the message restore completed, I see the database's status as
> LOADING. We are on Sql Server 2000 (8.00.818) on Windows 2000 Adv
> Servers.
> I ran dbcc on the source DB and it returned no errors. I tried the
> command 'restore db with recovery ' which didnot help. I get an message
> saying that the data file is only partially restored.. It seems the last
> resort is to change the status in system tables.

What does sp_helpdb say about the database?

If you run the RESTORE command from Query Analyzer, do you get any
interesting messages?

I think that what may have happened is that the database was restored
in such a way, that SQL Server now anticiapates one or more transaction
logs to be applied.

An example command to restore a database from QA:

RESTORE DATABASE db FROM DISK = 'C:\temp\whatever.dmp' WITH
MOVE 'datafile' TO 'C:\datadir\db.mdf',
MOVE 'logilfe' TO 'D:\logdir\db.ldf',
REPLACE, STATS

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Hi Thanks for the reply. sp_helpdb returns 0 rows. The same sql restore
using QA returns this error

"ConnectionRead (WrapperRead()). [SQLSTATE 01000] (Message 258)
General network error. Check your network documentation. [SQLSTATE
08S01] (Error 11) 10 percent restored. [SQLSTATE 01000] (Error 3211).
The step failed. "

But it restored fine once but when I tried again I got the above error.
The reasons could be 1. some timing limit ( Since I restore on the
server this should not be an issue.) 2. I see antivirus software trying
to scan the newly created data file.

Thanks for your time

Ragu|||Ragu (ragudba@.gmail.com) writes:
> Hi Thanks for the reply. sp_helpdb returns 0 rows.

Then the database is not there.

> The same sql restore using QA returns this error
> "ConnectionRead (WrapperRead()). [SQLSTATE 01000] (Message 258)
> General network error. Check your network documentation. [SQLSTATE
> 08S01] (Error 11) 10 percent restored. [SQLSTATE 01000] (Error 3211).
> The step failed. "

QA does not say "The step failed", does it? But, OK, I assume that it does
say "General network error" and all that jazz. That indicates that a tragic
accident occurred on the SQL Server side, and SQL Server had to terminate
the process. If you look in SQL Server's error log you are likely to find
a stack dump related to the accident. No, don't expect this stack dump
to make you that much wiser. But look there anyway.

> But it restored fine once but when I tried again I got the above error.
> The reasons could be 1. some timing limit ( Since I restore on the
> server this should not be an issue.) 2. I see antivirus software trying
> to scan the newly created data file.

I would certainly recommend preventing the antivirus stuff from sneaking
in.

What is funny is that you say that the backup loaded OK once. Had it never
loaded well I would suspect an accident in transport over the network. But,
hm, if I re-read your original message, not even then did the load complete
entirely successfully?

I would turn off the antivirus thing and try again. If it fails again,
I would try copying again. If I could find away to avoid the network,
I would try that. 20 GB is too much for a DVD, but a removable disk
that you connect over USB2 could be an alternative.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||HI Erland :

1. I will try to turn off the virus and try again.
2. I ran the query in QA on the server console using VPN and Remote
Connection and one thing or other always gets disconnected. So I put
the restore sql in a job and executed the job instead. Hence the words
"step failed"
3. But the error is the same in QA also.
4. Sometimes even thoug we get the same error in QA, DB after 3 hrs and
several "Bypassing recovery for database 'DB' because it is marked IN
LOAD." and one " Recovery is checkpointing database " messages, the DB
gets restored fine. The only message in the error log is Database "DB'
restore completed.
5. And in other environements with fatser servers ,we donot get this
error at all with the same backup file.

Thanks

Ragu|||Ragu (ragudba@.gmail.com) writes:
> 1. I will try to turn off the virus and try again.

If you have a virus on the machine, you should definitely turn if off! :-)

> 2. I ran the query in QA on the server console using VPN and Remote
> Connection and one thing or other always gets disconnected. So I put
> the restore sql in a job and executed the job instead. Hence the words
> "step failed"

I see.

If you run QA on the same machine as the server, and you get disconnected
that is likely to be a crash and not a network issue.

> 4. Sometimes even thoug we get the same error in QA, DB after 3 hrs and
> several "Bypassing recovery for database 'DB' because it is marked IN
> LOAD." and one " Recovery is checkpointing database " messages, the DB
> gets restored fine. The only message in the error log is Database "DB'
> restore completed.

Three hours to restore a 20 GB database? That appears to be a tad long
to me.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||1. I meant virus scan not virus per se.
2. Normally it takes 15 -20 minues on production servers.
3. Reg getting disconnedt while on the server, there was no crash. I
think that the error message is misleading.

Thanks for your responses.

ragu|||Another update. In the follwoing scenerio the restore was succesful.

1. created the db say DB1 on the server.

2, Using QA, run the sql

RESTORE DATABASE DB1 FROM DISK = 'c:\db_backup\DB.bak' with
move 'DB_Data' to 'c:\SQL_DATA\DB_RC4_Data.MDF',
move 'DB_Log' to 'c:\SQL_DATA\DB_RC4_Log.LDF',
REPLACE, STATS

3. After 15 min , got the error [Microsoft][ODBC SQL Server
Driver][Named Pipes]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent restored.
Connection Broken

4. The db looks fine. The tables,row count match. The db is healthy.

5. The error logs show s the same messages like starting up
datasbase,Bypassing recovery for database Db1because it is marked IN
LOAD ( 2 times ), Recovery is checkpointing database ,Database
restored: over a period of 37 minutes. ( We got error in QA after 15
minutes )

Ragu
Though the QA gave the error, the db restored fine.|||Ragu (ragudba@.gmail.com) writes:
> 1. I meant virus scan not virus per se.

I understand that. But it looked funny! :-)

I will have to look into your other post tonight. It looks very strange
to me.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Ragu (ragudba@.gmail.com) writes:
> 3. After 15 min , got the error [Microsoft][ODBC SQL Server
> Driver][Named Pipes]ConnectionRead (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent restored.
> Connection Broken

One thing is funny here. Did you really run the BACKUP command on a QA
which is on the same box as SQL Server? In such case I would not
expect Named Pipes in the error message.

The conclusion I am prepared to make, is that the network is flaky,
but SQL Server does not notice that client is gone and jogs along
with the restore. The recovery messages you get are funny, though.

If you really run QA on the server box, open Client Network Utility,
and check that you have share memory enabled (this is a check box
in the lower left corner).

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||HI I think you nailed the issue. Let us say if the database
Instance2\Database2 is running on DB server D02, and the network client
utility, there was entry for the Instance2\DB2 using namedpipes instead
of TCP. The share memory is enabled.

So The QA even though running on the same server connects as a client
using named pipes and that may be the issue.

I have removed the entry now and let me test it

Ragu|||Ragu (ragudba@.gmail.com) writes:
> HI I think you nailed the issue. Let us say if the database
> Instance2\Database2 is running on DB server D02, and the network client
> utility, there was entry for the Instance2\DB2 using namedpipes instead
> of TCP. The share memory is enabled.

So why does it not use shared memory? I have seen issues where shared
memory goes sour, but I seem to recall that in these cases you cannot
connect, or connection takes long time. If possible, may you should
retry rebooting the machine. (Not just only SQL Server. That's actually
how you can get shared memory to misbehave. Connect with QA on the local
server, restart the server without disconnecting the QA window.)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||No errors after this. tested few times and db got restored and no
errors were reported on QA. Thx for the help

ragu|||Ragu (ragudba@.gmail.com) writes:
> No errors after this. tested few times and db got restored and no
> errors were reported on QA. Thx for the help

Great to hear that it worked out!

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Restore database stuck on (Loading)

I recently installed MSDE on a laptop. I then restored several databases from backup files without problem. However, one database is constantly stuck at the grey colour displaying the (Loading) message.

Why won't this database restore ? It is of course the most important database and I only have the one backup file.

This only appears to fail on his server. Do I need to uninstall MSDE and start over ?It's probably the machine's "critical need detector", it might be a wee bit too sensitive or mis-adjusted.

On a slightly more serious note, what tools are you using to do the restore? The only tool that could do a restore that ships with MSDE is OSQL.EXE, and I'm pretty comfortable that you aren't using that! Enterprise Mangler would be my first guess, but that is still only a guess.

Could the dump (backup) have been made with a later service pack than you are using to restore it? That can make things get really crabby sometimes.

Is the database file one that this instance of MSDE can handle? Depending on the MSDE version, you can handle up to 2 Gb of data (although I've seen data and log dumps over 10 Gb).

If none of those ideas pan out, then my first suggestion would be to:

1 Disable everything you can that uses MSDE (keep notes!)
2 Stop the MSDE service
3 Restart the MSDE service
4 Try to load the offending database
5 If you can't load the database, stop the MSDE service
6 Examine the Errorlog file carefully
7 If you can't find anything in the Errorlog, consider posting it here.
8 if the database can be posted, consider posting the backup too for us to play with!

-PatP|||If it's in Loading state, could it be that you are restoring from a backup device that contained incomplete set of full db backup and some trx logs?|||But it restores without fail on any number of other servers. So I think the backup file is ok.

I have gone through the steps above and can't see anything wrong. I have pasted the errorlog below for perusal.

Yes I am using Enterprise manager. I also tried the restore database command from isqlw utility and that also produced the error :

Processed 8432 pages for database 'IPSHOW_NEW', file 'IPSHOW_Data' on file 1.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Processed 1 pages for database 'IPSHOW_NEW', file 'IPSHOW_Log' on file 1.

Connection Broken

Errorlog
2004-12-23 15:56:36.01 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2004-12-23 15:56:36.01 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-12-23 15:56:36.01 server All rights reserved.
2004-12-23 15:56:36.01 server Server Process ID is 1392.
2004-12-23 15:56:36.01 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2004-12-23 15:56:36.09 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-12-23 15:56:36.13 server SQL Server configured for thread mode processing.
2004-12-23 15:56:36.13 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-12-23 15:56:36.15 spid3 Starting up database 'master'.
2004-12-23 15:56:36.53 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-12-23 15:56:36.53 spid5 Starting up database 'model'.
2004-12-23 15:56:36.68 spid3 Server name is 'SBUTLER'.
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 4
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 5
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 6
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 9
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 10
2004-12-23 15:56:36.68 spid3 Starting up database 'IPSHOW_NEW'.
2004-12-23 15:56:36.68 server SQL server listening on 192.168.1.110: 1433.
2004-12-23 15:56:36.69 server SQL server listening on 127.0.0.1: 1433.
2004-12-23 15:56:36.98 spid3 Bypassing recovery for database 'IPSHOW_NEW' because it is marked IN LOAD.
2004-12-23 15:56:37.09 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-12-23 15:56:37.09 server SQL Server is ready for client connections
2004-12-23 15:56:37.22 spid5 Clearing tempdb database.
2004-12-23 15:56:38.58 spid5 Starting up database 'tempdb'.
2004-12-23 15:56:38.78 spid3 Recovery complete.
2004-12-23 15:56:38.78 spid3 SQL global counter collection task is created.
2004-12-23 15:57:35.63 spid51 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
2004-12-23 15:57:35.78 spid51 Starting up database 'msdb'.|||Post the statement used in ISQL to restore the database.
And ensure the backup file is stored on the MSDE server and if you are trying to restore from a network location due to th network issues it may be failing with the above error.

Refer to this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;827452 for relevancy.|||I gave up and uninstalled MSDE. As it turns out he required Reporting Services and a Developer Edition of SQL Server so all for the best in the end. Thanks for the assistance.

Restore database status displays Loading

Hello, I'm trying to restore one of our sql2k database and in Enterprise
Manager console it is greyed out and says (Loading). Can anyone help?
Thanks in advance.Did you refresh after the RESTORE operation? If not, do refresh.
Also, did you do the RESTORE using NORECOVERY? If not, do below:
RESTORE DATABASE dbname WITH RECOVERY
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"zz12" <IDontLikeSpam@.Nowhere.com> wrote in message news:OUmw8fOEIHA.3636@.TK2MSFTNGP03.phx.gbl...
> Hello, I'm trying to restore one of our sql2k database and in Enterprise
> Manager console it is greyed out and says (Loading). Can anyone help?
> Thanks in advance.
>|||I right clicked it and surprisingly it allowed me to redo the Restore
process which then seemed to went through ok.
Thanks a bunch Tibor for your speedy and helpful reply. Much appreciated.
Cheers :-)
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:6A73EF4C-F945-4BA7-B7B1-416656A35B4A@.microsoft.com...
> Did you refresh after the RESTORE operation? If not, do refresh.
> Also, did you do the RESTORE using NORECOVERY? If not, do below:
> RESTORE DATABASE dbname WITH RECOVERY
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "zz12" <IDontLikeSpam@.Nowhere.com> wrote in message
> news:OUmw8fOEIHA.3636@.TK2MSFTNGP03.phx.gbl...
>> Hello, I'm trying to restore one of our sql2k database and in Enterprise
>> Manager console it is greyed out and says (Loading). Can anyone help?
>> Thanks in advance.

Restore Database problem - LOADING forever

I had to restore a database late this afternoon. I have the database set to FULL recovery. Database backups are performed nightly and transaction log backups are performed every other hour. I decided to perform a point-in-time restore. When I restored this way everything seems to go ok and it finishes. Then the database is grayed and says "Loading". Although I tried 4 separate times, one time allowing over an hour, the grayed out database and "Loading" never goes away.

Freaking out I deleted the "Loading" database (didn't delete logs and backup files) and tried a manual restore from the previous night's backup file. It attached and restored properly and was ready to go in 2 minutes.

Of course I wanted to get the transaction log files restored too, since it had work from earlier today. So I tried another restore via point-in-time and got the same old messages. Currently, the database is running with the previous night's backup restored but the users aren't too keen on having to do 5 hours worth of work to catch up to the previous transaction log backup come Monday morning.

Any suggestions?

Thanks,
JBHow are you doing the restore? And why do you want to restore to a point in time?

Do it via query analyser with standby - this will enable you to look at the database between restores.

Do the full restore - look at it.

Now do the tr logs in turn - checking the database between each one.
Now you can do the last one with the point in time recovery.

If that fails then go back and redo up to the last one that restored successfully. At least you will lose at the most 2 hours.|||The poster probably did not click on Refresh menu item on Databases folder in EM.sql

restore database on SQL Server 6.5

Hi,
I restore a database using a 3rd party software. The
restore job was cancelled but the process "loading
database" is still in the output of "sp_who". I could not
kill it. Do I have to reboot the server to get rid of it
or I can start a job to continue to restore this database?
Thanks for help,Hi,
Try STOP and START the MSSQL Server service. After that start the Loading of
database again from ISQL_W.
LOAD database <dbname> from disk='c:\backup\dbname.DMP' with stats=10
Note: stats=10 will show the percentage of load completed.
Thanks
Hari
MCDBA
"Julia" <anonymous@.discussions.microsoft.com> wrote in message
news:1d83601c453e7$425a6e30$a401280a@.phx.gbl...
> Hi,
> I restore a database using a 3rd party software. The
> restore job was cancelled but the process "loading
> database" is still in the output of "sp_who". I could not
> kill it. Do I have to reboot the server to get rid of it
> or I can start a job to continue to restore this database?
> Thanks for help,

restore database (Loading) error

I am trying to restore a database from backup (Veritas)
The backup says it is restored successfully, but ....
in enterprise manager the database reads 'Data(loading)'
I tried two different distination names
two different sources.
With the same result.
I tried EXEC sp_delete_backuphistory '07/16/04'
based on something I found on the internet.
I am using SQL2000
Does anybody have any ideas?
Perhaps the Veritas software did not run recovery as the final step? This
will leave your db marked as loading, but you can run recovery manually.
RESTORE LOG mydb WITH RECOVERY
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"arniecds" <arniecds@.discussions.microsoft.com> wrote in message
news:113E17E0-6F53-4D9A-809F-F303063CC2F0@.microsoft.com...
> I am trying to restore a database from backup (Veritas)
> The backup says it is restored successfully, but ....
> in enterprise manager the database reads 'Data(loading)'
> I tried two different distination names
> two different sources.
> With the same result.
> I tried EXEC sp_delete_backuphistory '07/16/04'
> based on something I found on the internet.
> I am using SQL2000
> Does anybody have any ideas?
>

Restore Completes (Loading)

I have SQL Server 2000 Enterprise Edition with SP3A on my
Windows 2000 Advanced Server. There is only one
development database on this server.
When I restore a backup from this database onto another
server in a similiar environment the restore completes.
But database icon status, states that it is loading. I
refresh the databases (PF5) but it does not change.
Next, I run the restore database with recovery and the
restore completes.
Please help me resolve this issue.
Mike
RESTORE DATABASE DATABASE_NAME
from disk =
WITH RECOVERY
Are you sure that the environment is the same, or that there are no pending
transactions? According to BOL, the WITH RECOVERY option IS the default
option, and should only be required when a database upgrade is required.
Steve
RECOVERY
Instructs the restore operation to roll back any uncommitted transactions.
After the recovery process, the database is ready for use.
If subsequent RESTORE operations (RESTORE LOG, or RESTORE DATABASE from
differential) are planned, NORECOVERY or STANDBY should be specified
instead.
If neither NORECOVERY, RECOVERY, or STANDBY is specified, RECOVERY is the
default. When restoring backup sets from an earlier version of SQL Server, a
database upgrade may be required. This upgrade is performed automatically
when WITH RECOVERY is specified. For more information, see Transaction Log
Backups .
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:1deb101c4548a$985d2e00$a401280a@.phx.gbl...

> I have SQL Server 2000 Enterprise Edition with SP3A on my
> Windows 2000 Advanced Server. There is only one
> development database on this server.
> When I restore a backup from this database onto another
> server in a similiar environment the restore completes.
> But database icon status, states that it is loading. I
> refresh the databases (PF5) but it does not change.
> Next, I run the restore database with recovery and the
> restore completes.
> Please help me resolve this issue.
> Mike
>
> RESTORE DATABASE DATABASE_NAME
> from disk =
> WITH RECOVERY
>
|||HI,
It seems you have clicked the option "Non operational, need to load more
transaction logs" in enterprise manager while loading. Execute the below
command from query analyzer to recover the database:-
RESTORE DATABASE <dbname> with RECOVERY
Thanks
Hari
MCDBA
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:1deb101c4548a$985d2e00$a401280a@.phx.gbl...
> I have SQL Server 2000 Enterprise Edition with SP3A on my
> Windows 2000 Advanced Server. There is only one
> development database on this server.
> When I restore a backup from this database onto another
> server in a similiar environment the restore completes.
> But database icon status, states that it is loading. I
> refresh the databases (PF5) but it does not change.
> Next, I run the restore database with recovery and the
> restore completes.
> Please help me resolve this issue.
> Mike
>
> RESTORE DATABASE DATABASE_NAME
> from disk =
> WITH RECOVERY
>

Restore Completes (Loading)

I have SQL Server 2000 Enterprise Edition with SP3A on my
Windows 2000 Advanced Server. There is only one
development database on this server.
When I restore a backup from this database onto another
server in a similiar environment the restore completes.
But database icon status, states that it is loading. I
refresh the databases (PF5) but it does not change.
Next, I run the restore database with recovery and the
restore completes.
Please help me resolve this issue.
Mike
RESTORE DATABASE DATABASE_NAME
from disk =
WITH RECOVERYAre you sure that the environment is the same, or that there are no pending
transactions? According to BOL, the WITH RECOVERY option IS the default
option, and should only be required when a database upgrade is required.
Steve
RECOVERY
Instructs the restore operation to roll back any uncommitted transactions.
After the recovery process, the database is ready for use.
If subsequent RESTORE operations (RESTORE LOG, or RESTORE DATABASE from
differential) are planned, NORECOVERY or STANDBY should be specified
instead.
If neither NORECOVERY, RECOVERY, or STANDBY is specified, RECOVERY is the
default. When restoring backup sets from an earlier version of SQL Server, a
database upgrade may be required. This upgrade is performed automatically
when WITH RECOVERY is specified. For more information, see Transaction Log
Backups .
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:1deb101c4548a$985d2e00$a401280a@.phx
.gbl...

> I have SQL Server 2000 Enterprise Edition with SP3A on my
> Windows 2000 Advanced Server. There is only one
> development database on this server.
> When I restore a backup from this database onto another
> server in a similiar environment the restore completes.
> But database icon status, states that it is loading. I
> refresh the databases (PF5) but it does not change.
> Next, I run the restore database with recovery and the
> restore completes.
> Please help me resolve this issue.
> Mike
>
> RESTORE DATABASE DATABASE_NAME
> from disk =
> WITH RECOVERY
>|||HI,
It seems you have clicked the option "Non operational, need to load more
transaction logs" in enterprise manager while loading. Execute the below
command from query analyzer to recover the database:-
RESTORE DATABASE <dbname> with RECOVERY
Thanks
Hari
MCDBA
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:1deb101c4548a$985d2e00$a401280a@.phx
.gbl...
> I have SQL Server 2000 Enterprise Edition with SP3A on my
> Windows 2000 Advanced Server. There is only one
> development database on this server.
> When I restore a backup from this database onto another
> server in a similiar environment the restore completes.
> But database icon status, states that it is loading. I
> refresh the databases (PF5) but it does not change.
> Next, I run the restore database with recovery and the
> restore completes.
> Please help me resolve this issue.
> Mike
>
> RESTORE DATABASE DATABASE_NAME
> from disk =
> WITH RECOVERY
>

Restore Completes (Loading)

I have SQL Server 2000 Enterprise Edition with SP3A on my
Windows 2000 Advanced Server. There is only one
development database on this server.
When I restore a backup from this database onto another
server in a similiar environment the restore completes.
But database icon status, states that it is loading. I
refresh the databases (PF5) but it does not change.
Next, I run the restore database with recovery and the
restore completes.
Please help me resolve this issue.
Mike
RESTORE DATABASE DATABASE_NAME
from disk = WITH RECOVERYAre you sure that the environment is the same, or that there are no pending
transactions? According to BOL, the WITH RECOVERY option IS the default
option, and should only be required when a database upgrade is required.
Steve
RECOVERY
Instructs the restore operation to roll back any uncommitted transactions.
After the recovery process, the database is ready for use.
If subsequent RESTORE operations (RESTORE LOG, or RESTORE DATABASE from
differential) are planned, NORECOVERY or STANDBY should be specified
instead.
If neither NORECOVERY, RECOVERY, or STANDBY is specified, RECOVERY is the
default. When restoring backup sets from an earlier version of SQL Server, a
database upgrade may be required. This upgrade is performed automatically
when WITH RECOVERY is specified. For more information, see Transaction Log
Backups .
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:1deb101c4548a$985d2e00$a401280a@.phx.gbl...
> I have SQL Server 2000 Enterprise Edition with SP3A on my
> Windows 2000 Advanced Server. There is only one
> development database on this server.
> When I restore a backup from this database onto another
> server in a similiar environment the restore completes.
> But database icon status, states that it is loading. I
> refresh the databases (PF5) but it does not change.
> Next, I run the restore database with recovery and the
> restore completes.
> Please help me resolve this issue.
> Mike
>
> RESTORE DATABASE DATABASE_NAME
> from disk => WITH RECOVERY
>|||HI,
It seems you have clicked the option "Non operational, need to load more
transaction logs" in enterprise manager while loading. Execute the below
command from query analyzer to recover the database:-
RESTORE DATABASE <dbname> with RECOVERY
Thanks
Hari
MCDBA
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:1deb101c4548a$985d2e00$a401280a@.phx.gbl...
> I have SQL Server 2000 Enterprise Edition with SP3A on my
> Windows 2000 Advanced Server. There is only one
> development database on this server.
> When I restore a backup from this database onto another
> server in a similiar environment the restore completes.
> But database icon status, states that it is loading. I
> refresh the databases (PF5) but it does not change.
> Next, I run the restore database with recovery and the
> restore completes.
> Please help me resolve this issue.
> Mike
>
> RESTORE DATABASE DATABASE_NAME
> from disk => WITH RECOVERY
>

Restore a DB

Hi,
I've restored a DB with 6.5 GB.
Now the DB is loading over 5 hours!!!
What is the DB doing?
How long could it take?
br
CharlieThat seems a bit long. Have you checked the errorlog? How about using
perfmon.exe to see if CPU or disk is currently busy?
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Charlie Schaubmair" <CharlieSchaubmair@.discussions.microsoft.com> wrote in
message news:117C3217-812F-4689-B963-52029F71B161@.microsoft.com...
> Hi,
> I've restored a DB with 6.5 GB.
> Now the DB is loading over 5 hours!!!
> What is the DB doing?
> How long could it take?
> br
> Charlie

Restore a DB

Hi,
I've restored a DB with 6.5 GB.
Now the DB is loading over 5 hours!!!
What is the DB doing?
How long could it take?
br
Charlie
That seems a bit long. Have you checked the errorlog? How about using
perfmon.exe to see if CPU or disk is currently busy?
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Charlie Schaubmair" <CharlieSchaubmair@.discussions.microsoft.com> wrote in
message news:117C3217-812F-4689-B963-52029F71B161@.microsoft.com...
> Hi,
> I've restored a DB with 6.5 GB.
> Now the DB is loading over 5 hours!!!
> What is the DB doing?
> How long could it take?
> br
> Charlie

Restore a DB

Hi,
I've restored a DB with 6.5 GB.
Now the DB is loading over 5 hours!!!
What is the DB doing?
How long could it take?
br
CharlieThat seems a bit long. Have you checked the errorlog? How about using
perfmon.exe to see if CPU or disk is currently busy?
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Charlie Schaubmair" <CharlieSchaubmair@.discussions.microsoft.com> wrote in
message news:117C3217-812F-4689-B963-52029F71B161@.microsoft.com...
> Hi,
> I've restored a DB with 6.5 GB.
> Now the DB is loading over 5 hours!!!
> What is the DB doing?
> How long could it take?
> br
> Charlie