I/O error (bad page id)

We can't get the database restored. It won't reattach
(sp_attach_db) and it won't restore from a backup file.
So we have the Mdf and Ldf files and a backup file but
since we detached, we can't seem to get the data on-line
again to do anything.
Any attempts to repair the database with CHECKDB results
in consistency errors. The database can be backed up but
not restored from a recent database backup. We tried to
recreate the database by using Copy Database Wizard and
DTS both with no success because of an I/O error. Trying
to query tables sometimes worked and other times didn't.
Finally, the database was detached and ended any attempts
to re-attach thus far.
Server: Msg 7995, Level 16, State 1, Line 1
Database 'woodsch0304' consistency errors in sysobjects,
sysindexes, syscolumns, or systypes prevent further
CHECKDB processing.
Not giving up yet...If the database has any value to you, it is time to open a call to MS PSS. I
think the cost is still $249.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> We can't get the database restored. It won't reattach
> (sp_attach_db) and it won't restore from a backup file.
> So we have the Mdf and Ldf files and a backup file but
> since we detached, we can't seem to get the data on-line
> again to do anything.
> Any attempts to repair the database with CHECKDB results
> in consistency errors. The database can be backed up but
> not restored from a recent database backup. We tried to
> recreate the database by using Copy Database Wizard and
> DTS both with no success because of an I/O error. Trying
> to query tables sometimes worked and other times didn't.
> Finally, the database was detached and ended any attempts
> to re-attach thus far.
> Server: Msg 7995, Level 16, State 1, Line 1
> Database 'woodsch0304' consistency errors in sysobjects,
> sysindexes, syscolumns, or systypes prevent further
> CHECKDB processing.
>
> Not giving up yet...
>|||You've lost a page in one of the critical (for CHECKDB and database use)
system tables so you're in danger of losing your database. I concur with
Wayne's suggestion - PSS is your best bet.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eGoGOWkJEHA.624@.TK2MSFTNGP11.phx.gbl...
> If the database has any value to you, it is time to open a call to MS PSS.
I
> think the cost is still $249.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
> news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> > We can't get the database restored. It won't reattach
> > (sp_attach_db) and it won't restore from a backup file.
> >
> > So we have the Mdf and Ldf files and a backup file but
> > since we detached, we can't seem to get the data on-line
> > again to do anything.
> >
> > Any attempts to repair the database with CHECKDB results
> > in consistency errors. The database can be backed up but
> > not restored from a recent database backup. We tried to
> > recreate the database by using Copy Database Wizard and
> > DTS both with no success because of an I/O error. Trying
> > to query tables sometimes worked and other times didn't.
> >
> > Finally, the database was detached and ended any attempts
> > to re-attach thus far.
> >
> > Server: Msg 7995, Level 16, State 1, Line 1
> >
> > Database 'woodsch0304' consistency errors in sysobjects,
> > sysindexes, syscolumns, or systypes prevent further
> > CHECKDB processing.
> >
> >
> > Not giving up yet...
> >
>