Database Status = Loading

A coworker is repeatedly experiencing problems restoring database backups on
a new sql virtual server (clustered). He has restored a database backup
using enterprise manager. Enterprise manager told him that the restore has
completed without giving any errors. We can not access the database and
enterprise manager shows the status of the database as "Loading". I ran the
command RESTORE DATABASE <databasename> WITH RECOVERY and received an error
basically saying that the database was not completely loaded or the restore
did not complete. Can anyone tell me what the problem is or tell me how to
avoid this scenario?
-SJHi
Have you checked the SQL Server log and the System Event log to see if there
is any additional information in them?
It is usually a good idea to post the exact error numbers and messages.
John
"SJ" wrote:

> A coworker is repeatedly experiencing problems restoring database backups
on
> a new sql virtual server (clustered). He has restored a database backup
> using enterprise manager. Enterprise manager told him that the restore ha
s
> completed without giving any errors. We can not access the database and
> enterprise manager shows the status of the database as "Loading". I ran t
he
> command RESTORE DATABASE <databasename> WITH RECOVERY and received an erro
r
> basically saying that the database was not completely loaded or the restor
e
> did not complete. Can anyone tell me what the problem is or tell me how t
o
> avoid this scenario?
> --
> -SJ|||Here is the error:
File '<logical file name>' was only partially restored by a database or file
restore. The entire file must be successfully restored before applying the
log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Enterprise manager told me "Restore of database '<databasename>' completed
successfully."
-SJ
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you checked the SQL Server log and the System Event log to see if the
re
> is any additional information in them?
> It is usually a good idea to post the exact error numbers and messages.
> John
> "SJ" wrote:
>|||Hi SJ
Check out:
http://groups.google.com/group/micr...27357de5278e8bd
John
"SJ" wrote:
[vbcol=seagreen]
> Here is the error:
> File '<logical file name>' was only partially restored by a database or fi
le
> restore. The entire file must be successfully restored before applying the
> log.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> Enterprise manager told me "Restore of database '<databasename>' completed
> successfully."
> -SJ
> "John Bell" wrote:
>

Database Status = Loading

A coworker is repeatedly experiencing problems restoring database backups on
a new sql virtual server (clustered). He has restored a database backup
using enterprise manager. Enterprise manager told him that the restore has
completed without giving any errors. We can not access the database and
enterprise manager shows the status of the database as "Loading". I ran the
command RESTORE DATABASE <databasename> WITH RECOVERY and received an error
basically saying that the database was not completely loaded or the restore
did not complete. Can anyone tell me what the problem is or tell me how to
avoid this scenario?
-SJ
Hi
Have you checked the SQL Server log and the System Event log to see if there
is any additional information in them?
It is usually a good idea to post the exact error numbers and messages.
John
"SJ" wrote:

> A coworker is repeatedly experiencing problems restoring database backups on
> a new sql virtual server (clustered). He has restored a database backup
> using enterprise manager. Enterprise manager told him that the restore has
> completed without giving any errors. We can not access the database and
> enterprise manager shows the status of the database as "Loading". I ran the
> command RESTORE DATABASE <databasename> WITH RECOVERY and received an error
> basically saying that the database was not completely loaded or the restore
> did not complete. Can anyone tell me what the problem is or tell me how to
> avoid this scenario?
> --
> -SJ
|||Here is the error:
File '<logical file name>' was only partially restored by a database or file
restore. The entire file must be successfully restored before applying the
log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Enterprise manager told me "Restore of database '<databasename>' completed
successfully."
-SJ
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you checked the SQL Server log and the System Event log to see if there
> is any additional information in them?
> It is usually a good idea to post the exact error numbers and messages.
> John
> "SJ" wrote:
|||Hi SJ
Check out:
http://groups.google.com/group/micro...7357de5278e8bd
John
"SJ" wrote:
[vbcol=seagreen]
> Here is the error:
> File '<logical file name>' was only partially restored by a database or file
> restore. The entire file must be successfully restored before applying the
> log.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> Enterprise manager told me "Restore of database '<databasename>' completed
> successfully."
> -SJ
> "John Bell" wrote:

Database Status = Loading

A coworker is repeatedly experiencing problems restoring database backups on
a new sql virtual server (clustered). He has restored a database backup
using enterprise manager. Enterprise manager told him that the restore has
completed without giving any errors. We can not access the database and
enterprise manager shows the status of the database as "Loading". I ran the
command RESTORE DATABASE <databasename> WITH RECOVERY and received an error
basically saying that the database was not completely loaded or the restore
did not complete. Can anyone tell me what the problem is or tell me how to
avoid this scenario?
--
-SJHi
Have you checked the SQL Server log and the System Event log to see if there
is any additional information in them?
It is usually a good idea to post the exact error numbers and messages.
John
"SJ" wrote:
> A coworker is repeatedly experiencing problems restoring database backups on
> a new sql virtual server (clustered). He has restored a database backup
> using enterprise manager. Enterprise manager told him that the restore has
> completed without giving any errors. We can not access the database and
> enterprise manager shows the status of the database as "Loading". I ran the
> command RESTORE DATABASE <databasename> WITH RECOVERY and received an error
> basically saying that the database was not completely loaded or the restore
> did not complete. Can anyone tell me what the problem is or tell me how to
> avoid this scenario?
> --
> -SJ|||Here is the error:
File '<logical file name>' was only partially restored by a database or file
restore. The entire file must be successfully restored before applying the
log.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Enterprise manager told me "Restore of database '<databasename>' completed
successfully."
-SJ
"John Bell" wrote:
> Hi
> Have you checked the SQL Server log and the System Event log to see if there
> is any additional information in them?
> It is usually a good idea to post the exact error numbers and messages.
> John
> "SJ" wrote:
> > A coworker is repeatedly experiencing problems restoring database backups on
> > a new sql virtual server (clustered). He has restored a database backup
> > using enterprise manager. Enterprise manager told him that the restore has
> > completed without giving any errors. We can not access the database and
> > enterprise manager shows the status of the database as "Loading". I ran the
> > command RESTORE DATABASE <databasename> WITH RECOVERY and received an error
> > basically saying that the database was not completely loaded or the restore
> > did not complete. Can anyone tell me what the problem is or tell me how to
> > avoid this scenario?
> >
> > --
> > -SJ|||Hi SJ
Check out:
http://groups.google.com/group/microsoft.public.sqlserver.clients/browse_frm/thread/b5447588fe32acf0/527357de5278e8bd#527357de5278e8bd
John
"SJ" wrote:
> Here is the error:
> File '<logical file name>' was only partially restored by a database or file
> restore. The entire file must be successfully restored before applying the
> log.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> Enterprise manager told me "Restore of database '<databasename>' completed
> successfully."
> -SJ
> "John Bell" wrote:
> > Hi
> >
> > Have you checked the SQL Server log and the System Event log to see if there
> > is any additional information in them?
> >
> > It is usually a good idea to post the exact error numbers and messages.
> >
> > John
> >
> > "SJ" wrote:
> >
> > > A coworker is repeatedly experiencing problems restoring database backups on
> > > a new sql virtual server (clustered). He has restored a database backup
> > > using enterprise manager. Enterprise manager told him that the restore has
> > > completed without giving any errors. We can not access the database and
> > > enterprise manager shows the status of the database as "Loading". I ran the
> > > command RESTORE DATABASE <databasename> WITH RECOVERY and received an error
> > > basically saying that the database was not completely loaded or the restore
> > > did not complete. Can anyone tell me what the problem is or tell me how to
> > > avoid this scenario?
> > >
> > > --
> > > -SJ

database restored, publications gone

hi all,

our datbase was restore but the publications were all gone.

however replication monitor shows publication and subscription.

worst. can create the publication with the same name because

it raises an error saying that it can't drop publication becuase

there is a subscription in it.

how can i remove the publication when the are already gone in the publication

folder but exist in the replication monitor

thanks for the help

if you want to preserve replication when you restore a backup of a published database, specify "KEEP_REPLICATION" with your RESTORE command.

To remove replication from a published database, try sp_removedbreplication.

|||

thanks, i already resolve the issue.

i disabled the publications in the rep monitor and then delete its contents

Database Restore failed, now inaccessible and can not restore.

I have seen this before. A 2000 restore fails, leaving the database thinking it is being restored but the restore job failed and errors when it is restarted. EM is clueless. I believe there is a proc to reset some flag. Can you share it with me?

Thanks!

sp_resetstatus|||I don't know if being marked "suspect" is the same as being marked as being restored. Is it?|||

if you have backup files, then try to restore it from QA. the problem may be when you restore the data file and log file ; the datafile step may be success and the log file may not. untill unless it find WITH RECOVERy option the database status will be "restoring" . So what you do is , take the backup set and restore it with someother name using WITH Move option

Madhu

|||no. 'suspect' is not the same as 'restoring'. sp_resetstatus only handles 'suspect' status.

To get out of restoring, you will need to recover the database. Try:

restore database <db> with recovery

database restore

How does the database restore work... ?
when a database is backed up and restored on a new device/server will that create new data pages?
or
Is it like uncompressing the data and index pages?
ThanksWhy does it matter?

database refreshed using backup restore

Is there a system table or a way that allows you to check
when was the last time the database was refreshed (backup
restored) ? Sysdatabases shows the db creation date.use msdb
go
select * from restorehistory
go
"J Reyes" <anonymous@.discussions.microsoft.com> wrote in message
news:155501c4f4d0$eb3dd750$a601280a@.phx.gbl...
> Is there a system table or a way that allows you to check
> when was the last time the database was refreshed (backup
> restored) ? Sysdatabases shows the db creation date.
>

Database Recovery

i have a database which restored with a null database. how can i recover my previous data? i have no backup.

It is not clear what you mean by 'null database'.

IF you have restored a database from a 'empty' database (either by replacing the files or using a backup), and IF you do not have another backup with data -you are out of luck and need to quickly type up and send out your rsum.

There is no way to recover data that doesn't exist (except for re-entering it by hand), and without backups, in your situation, it appears that the data no longer exist.

|||

Arnie Rowland wrote:

It is not clear what you mean by 'null database'.

IF you have restored a database from a 'empty' database (either by replacing the files or using a backup), and IF you do not have another backup with data -you are out of luck and need to quickly type up and send out your rsum.

There is no way to recover data that doesn't exist (except for re-entering it by hand), and without backups, in your situation, it appears that the data no longer exist.

i restore it with a wrong backup file. really there is no way?|||

The restore will have overwritten the data files so you won't be able to get anything from the current database.

If you have a disk backup you might be able to attach the .mdf otherwise if you don't have a backup then I'm afraid you've lost it.

|||Unfortunately, DBA skillsets STILL do not include magic! (Although at times it may seek like we do practice the 'black arts' ... Mostly, just sticking pins in PM dolls ... )

database recovery

hai!
i have a database which crashed recently(26th sep 2007).my last backup is on 14 sep 2007.i have restored database after two days.Now i have a database (old) with data upto 14sep 2007 and from 26sep to till date.(data from 14sep to 26sep missing).I restored database on 28th with a new database name which has data upto 26th sep 2007.how to attach these two databases to a single database to have data from beginning to tilldate.

please help in this regard.in the future, if you want to be able to recover all of your data you should place your databases in full recovery, take full and transaction logs back ups, have you mdfs and ldfs on seperate drives and make sure your your backups are stored on a tape drive or another server and maybe keep a copy off site.

as for your current situation, it sounds like you are going to have to stitch this one together by copying your tables from one database into the tables of the database you want to hold all of your data.

Database recovery

Had a server crash totaly. Rebuilt a new server with
different drive partitions. Reinstalled SQL 7 and then
restored master from backup. SQL will not start because
it is looking for model,msdb, temp in the original
location which no longer exists. Had this problem on 2000
as well. Any suggestions?You can try to start SQL Server with two undocumented trace flags:
Trace Flag 3608 does not recover any database except the master
Trace Flag 3609 start without TempDB.
Start the service with -f (minimal configuration) option as well.
If this works, attach the databases, except tempdb. Try to move tempdb to a
new location as described in the "Expanding a Database" topic in BOL
(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\cr
eatedb.chm::/cm_8_des_03_71d1.htm). If this works, restart SQL Server.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Franco" <franco.carusi@.sbs.siemens.co.za> wrote in message
news:018401c37cdc$b94d0df0$a001280a@.phx.gbl...
> Had a server crash totaly. Rebuilt a new server with
> different drive partitions. Reinstalled SQL 7 and then
> restored master from backup. SQL will not start because
> it is looking for model,msdb, temp in the original
> location which no longer exists. Had this problem on 2000
> as well. Any suggestions?|||Unfortunately a list of undocumented trace flags does not exist in public,
otherwise they would not be undocumented. What you can do is not to restore
the master db after reinstallation, you can just use the "new" one and
attach other databases. But you would have to recreate all logins, map them
to db users etc. The other solution is to call MS support. I think they have
the list:-)
Have you tried with all three, the -f option and both trace flags mentioned
at the same time? I remember few years ago when I had some problems with
tempdb these options forced SQL Sever to skip recovery for all databases,
not just model.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Franco" <franco.carusi@.sbs.siemens.co.za> wrote in message
news:08d101c37cf0$7f7ed680$a401280a@.phx.gbl...
> Tried it and does not work - from the error log it seems
> as if it skipped the model database but is still looking
> for msdb and temp. (previously looking for msdb and
> model). Definately looks as if a step closer. Do you know
> where I can get a list of trace flags?
> >--Original Message--
> >You can try to start SQL Server with two undocumented
> trace flags:
> >Trace Flag 3608 does not recover any database except the
> master
> >Trace Flag 3609 start without TempDB.
> >Start the service with -f (minimal configuration) option
> as well.
> >If this works, attach the databases, except tempdb. Try
> to move tempdb to a
> >new location as described in the "Expanding a Database"
> topic in BOL
> >(mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%
> 20Server\80\Tools\Books\cr
> >eatedb.chm::/cm_8_des_03_71d1.htm). If this works,
> restart SQL Server.
> >
> >--
> >Dejan Sarka, SQL Server MVP
> >FAQ from Neil & others at: http://www.sqlserverfaq.com
> >Please reply only to the newsgroups.
> >PASS - the definitive, global community
> >for SQL Server professionals - http://www.sqlpass.org
> >
> >"Franco" <franco.carusi@.sbs.siemens.co.za> wrote in
> message
> >news:018401c37cdc$b94d0df0$a001280a@.phx.gbl...
> >> Had a server crash totaly. Rebuilt a new server with
> >> different drive partitions. Reinstalled SQL 7 and then
> >> restored master from backup. SQL will not start because
> >> it is looking for model,msdb, temp in the original
> >> location which no longer exists. Had this problem on
> 2000
> >> as well. Any suggestions?
> >
> >
> >.
> >

Database Overwritten

We run SQL 2000 SP3a. I restored both DB and LOG files and re-attached the
database and all went well. However, this database has been overwritten
somehow. We definitely have not restored any further files from tape.
The "Date Modified" has been changed on the DB and LOG files. At this time
the SQL Server Logs show "Process ID 54 killed by hostname MYSERVER, host
process ID 3740", followed by "Starting up database 'MYDATABASE'", then
"Analysis of database 'MYDATABASE' (8) is 100% complete (approximately 0 more
seconds)", then "Error: 15457, Severity: 0, State: 1" and finally
"Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement to install.."
We have no Database Maintenance Plans in place. Our backups our taken by
CommVault Galaxy and this shows no restores. I need to find out what has
happened. Can anybody help?My guess, from the messages, is that someone ran sp_detach_db and then sp_attach_db. But, AFAIK,
there's no more logged that what you have now...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Gerrry" <Gerrry@.discussions.microsoft.com> wrote in message
news:464F2B26-54FC-4C36-8F71-E2450B0B6559@.microsoft.com...
> We run SQL 2000 SP3a. I restored both DB and LOG files and re-attached the
> database and all went well. However, this database has been overwritten
> somehow. We definitely have not restored any further files from tape.
> The "Date Modified" has been changed on the DB and LOG files. At this time
> the SQL Server Logs show "Process ID 54 killed by hostname MYSERVER, host
> process ID 3740", followed by "Starting up database 'MYDATABASE'", then
> "Analysis of database 'MYDATABASE' (8) is 100% complete (approximately 0 more
> seconds)", then "Error: 15457, Severity: 0, State: 1" and finally
> "Configuration option 'show advanced options' changed from 1 to 1. Run the
> RECONFIGURE statement to install.."
> We have no Database Maintenance Plans in place. Our backups our taken by
> CommVault Galaxy and this shows no restores. I need to find out what has
> happened. Can anybody help?

Database Overwritten

We run SQL 2000 SP3a. I restored both DB and LOG files and re-attached the
database and all went well. However, this database has been overwritten
somehow. We definitely have not restored any further files from tape.
The "Date Modified" has been changed on the DB and LOG files. At this time
the SQL Server Logs show "Process ID 54 killed by hostname MYSERVER, host
process ID 3740", followed by "Starting up database 'MYDATABASE'", then
"Analysis of database 'MYDATABASE' (8) is 100% complete (approximately 0 more
seconds)", then "Error: 15457, Severity: 0, State: 1" and finally
"Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement to install.."
We have no Database Maintenance Plans in place. Our backups our taken by
CommVault Galaxy and this shows no restores. I need to find out what has
happened. Can anybody help?
My guess, from the messages, is that someone ran sp_detach_db and then sp_attach_db. But, AFAIK,
there's no more logged that what you have now...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Gerrry" <Gerrry@.discussions.microsoft.com> wrote in message
news:464F2B26-54FC-4C36-8F71-E2450B0B6559@.microsoft.com...
> We run SQL 2000 SP3a. I restored both DB and LOG files and re-attached the
> database and all went well. However, this database has been overwritten
> somehow. We definitely have not restored any further files from tape.
> The "Date Modified" has been changed on the DB and LOG files. At this time
> the SQL Server Logs show "Process ID 54 killed by hostname MYSERVER, host
> process ID 3740", followed by "Starting up database 'MYDATABASE'", then
> "Analysis of database 'MYDATABASE' (8) is 100% complete (approximately 0 more
> seconds)", then "Error: 15457, Severity: 0, State: 1" and finally
> "Configuration option 'show advanced options' changed from 1 to 1. Run the
> RECONFIGURE statement to install.."
> We have no Database Maintenance Plans in place. Our backups our taken by
> CommVault Galaxy and this shows no restores. I need to find out what has
> happened. Can anybody help?

Database Overwritten

We run SQL 2000 SP3a. I restored both DB and LOG files and re-attached the
database and all went well. However, this database has been overwritten
somehow. We definitely have not restored any further files from tape.
The "Date Modified" has been changed on the DB and LOG files. At this time
the SQL Server Logs show "Process ID 54 killed by hostname MYSERVER, host
process ID 3740", followed by "Starting up database 'MYDATABASE'", then
"Analysis of database 'MYDATABASE' (8) is 100% complete (approximately 0 mor
e
seconds)", then "Error: 15457, Severity: 0, State: 1" and finally
"Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement to install.."
We have no Database Maintenance Plans in place. Our backups our taken by
CommVault Galaxy and this shows no restores. I need to find out what has
happened. Can anybody help?My guess, from the messages, is that someone ran sp_detach_db and then sp_a
ttach_db. But, AFAIK,
there's no more logged that what you have now...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Gerrry" <Gerrry@.discussions.microsoft.com> wrote in message
news:464F2B26-54FC-4C36-8F71-E2450B0B6559@.microsoft.com...
> We run SQL 2000 SP3a. I restored both DB and LOG files and re-attached the
> database and all went well. However, this database has been overwritten
> somehow. We definitely have not restored any further files from tape.
> The "Date Modified" has been changed on the DB and LOG files. At this time
> the SQL Server Logs show "Process ID 54 killed by hostname MYSERVER, host
> process ID 3740", followed by "Starting up database 'MYDATABASE'", then
> "Analysis of database 'MYDATABASE' (8) is 100% complete (approximately 0 m
ore
> seconds)", then "Error: 15457, Severity: 0, State: 1" and finally
> "Configuration option 'show advanced options' changed from 1 to 1. Run the
> RECONFIGURE statement to install.."
> We have no Database Maintenance Plans in place. Our backups our taken by
> CommVault Galaxy and this shows no restores. I need to find out what has
> happened. Can anybody help?