Restore stays in load status after restore norecovery

windows 2003, sql2000, sp3a - load 100gb database from a full backup (in EM)
and remains in load status (I was sure I had it set to recover). note: No t
ranslogs backups ever are produced for this db. No errors I believe when
it completed, although I di
d not look at the msg box too carefully, and clicked ok.
Although I later did a restore with norecovery anyway, it says the following
, any thoughts ?
thanks
Kw
file 'JDE_PRODUCTION_Data' 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.sounds a bad backup. Can you reproduce the error by doing another restore
through Query analyzer?
"kw" <anonymous@.discussions.microsoft.com> wrote in message
news:03E527B2-999A-4DE8-8D2E-6EA3387C2E67@.microsoft.com...

quote:

---

> windows 2003, sql2000, sp3a - load 100gb database from a full backup (in

---

EM) and remains in load status (I was sure I had it set to recover). note:
No translogs backups ever are produced for this db. No errors I believe
when it completed, although I did not look at the msg box too carefully, and
clicked ok.

quote:

---

> Although I later did a restore with norecovery anyway, it says the

---

following, any thoughts ?

quote:

---

> thanks
> Kw
> file 'JDE_PRODUCTION_Data' was only partially restored by a database or

---

file restore. The entire file must be successfully restored before applying
the log.

quote:

---

> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>

---

Restore stays in load status after restore norecovery

windows 2003, sql2000, sp3a - load 100gb database from a full backup (in EM) and remains in load status (I was sure I had it set to recover). note: No translogs backups ever are produced for this db. No errors I believe when it completed, although I did not look at the msg box too carefully, and clicked ok.
Although I later did a restore with norecovery anyway, it says the following, any thoughts ?
thanks
Kw
file 'JDE_PRODUCTION_Data' 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.sounds a bad backup. Can you reproduce the error by doing another restore
through Query analyzer?
"kw" <anonymous@.discussions.microsoft.com> wrote in message
news:03E527B2-999A-4DE8-8D2E-6EA3387C2E67@.microsoft.com...
> windows 2003, sql2000, sp3a - load 100gb database from a full backup (in
EM) and remains in load status (I was sure I had it set to recover). note:
No translogs backups ever are produced for this db. No errors I believe
when it completed, although I did not look at the msg box too carefully, and
clicked ok.
> Although I later did a restore with norecovery anyway, it says the
following, any thoughts ?
> thanks
> Kw
> file 'JDE_PRODUCTION_Data' 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.
>

Restore MDF problem

typical "user didn't backup database before performing transactions" case. (note: below I have renamed my mdf file as my_data.mdf for privacy purposes)

I'm trying to attach an mdf that I pulled off my server into my local database in SQL 2005 but get this error during the attach process:

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'BG-PC43'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:1022464; actual 0:0). It occurred during a read of page (1:1022464) in database ID 9 at offset 0x000001f3400000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\my_Data.MDF'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Could not open new database 'RMTEST'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 824)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=824&LinkId=20476

BUTTONS:

OK

looks like that database is corrupted. You should restore from an earlier/different backup.

Restore MDF problem

typical "user didn't backup database before performing transactions" case. (note: below I have renamed my mdf file as my_data.mdf for privacy purposes)

I'm trying to attach an mdf that I pulled off my server into my local database in SQL 2005 but get this error during the attach process:

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'BG-PC43'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:1022464; actual 0:0). It occurred during a read of page (1:1022464) in database ID 9 at offset 0x000001f3400000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\my_Data.MDF'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Could not open new database 'RMTEST'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 824)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=824&LinkId=20476

BUTTONS:

OK

looks like that database is corrupted. You should restore from an earlier/different backup.