Re: Corrupt backup - "An internal consistency error occurred", code 42000
From: Kris Shier (ks4hire_at__NOSPAM_yahoo.com)
Date: 05/14/04
- Next message: Dan: "questions about logging"
- Previous message: Ysandre: "Re: DTS"
- In reply to: Sue Hoegemeier: "Re: Corrupt backup - "An internal consistency error occurred", code 42000"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 14 May 2004 15:25:58 -0400
Thanks for the info!
"Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
news:q7i5a05g0objjrt77root0kjk4583no15h@4ax.com...
> Are you running DBCC CHECKDB on a regular basis before your
> backups?
Uh... now I am! :D
Yesterday, DBCC CHECKDB reported no errors on the 'base, though, and then I
got the same error again when trying to restore it on the production server.
I was able to successfully mount the database by manually attaching the mdf
file, though. ('Plan B')
I spent most of the day working with it, doing import and export operations.
At the end of the day, I deleted all the temp data, ran DBCC CHECKDB (which
showed no errors), and did a backup. I was able to successfully restore
this backup onto my dev server. We'll see Monday if the reverse holds true.
I suspect something about the data I was importing was somehow 'invalid',
but I really have no idea what. I would expect that DTS operations would
throw an error up-front if you are trying to load some kind of data that
could potentially corrupt the database.
Anyone, any comments on this?
Thanks!
- Next message: Dan: "questions about logging"
- Previous message: Ysandre: "Re: DTS"
- In reply to: Sue Hoegemeier: "Re: Corrupt backup - "An internal consistency error occurred", code 42000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|