Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
satshergill
Starting Member
2 Posts |
Posted - 2007-01-30 : 10:25:49
|
Hi allI have a database that is being restored to another instance of SQL server 2000 sp4 by attatching the mdf and ldf files. I then run EXEC sp_change_users_login to sync the users. When I try to run some delete commands on the new restored database I get 'Fatal error 8908'I then run a DBCC CHECKDB on the database and told to run it again with REPAIR_ALLOW_DATA_LOSSI have noticed that when I create a new databse and restore a .bak over this the delete commands work.Am I correct in thinking that I can get rid of the corruption on the original database by creating a new database then restoring a valid .bak backup on this new database. |
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-01-30 : 10:36:33
|
The original database is corrupt, and the backup file you're using doesn't seem to have the corruption in it (I'm guessing its not a very recent backup).How old is the backup?Paul RandalPrincipal Lead Program Manager, Microsoft SQL Server Core Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)http://blogs.msdn.com/sqlserverstorageengine/default.aspx |
|
|
MohammedU
Posting Yak Master
145 Posts |
Posted - 2007-01-31 : 00:58:50
|
May be your attached db got corrupted...or As Paul mentioned your db backup is not current..Did you run DBCC CHECKDB on the original server?MohammedU |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-01-31 : 01:31:31
|
btw, REPAIR_ALLOW_DATA_LOSS is never that good of an option to use. Best to go back to a valid backup and roll through the tlogs to get it current. Unless you don't have the database in FULL log mode and are not taking regular backups. -ec |
|
|
|
|
|