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 |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2006-06-22 : 09:45:38
|
raju writes "while attaching the mdf file we are getting the following errorerror 823i/o error (bad page id) detected during read at offset0x0000001404000 in file d:\filename" |
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2006-06-22 : 13:59:55
|
Dare I ask if you have a backup?Paul RandalLead Program Manager, Microsoft SQL Server Storage Engine + SQL Express(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
mfdarvesh
Starting Member
10 Posts |
Posted - 2008-06-10 : 02:19:05
|
same problem with happened due to power failure. Do not have any backup with and database is at attaching, is there any way to repair that database? |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2008-06-16 : 14:27:31
|
Yes, you can run DBCC CHECKDB with the REPAIR_ALLOW_DATA_LOSS option. Depending on what kind of page is corrupt, you may lose data.Paul RandalSQL Server MVP, Managing Director, SQLskills.com |
|
|
surya_rakanta
Starting Member
19 Posts |
Posted - 2008-07-30 : 23:49:06
|
quote: Originally posted by AskSQLTeam raju writes "while attaching the mdf file we are getting the following errorerror 823i/o error (bad page id) detected during read at offset0x0000001404000 in file d:\filename"
----------If you are using MS SQL Server 2000, you should checks for the given offset in physical file (using some hex editor) and checks for sign of torn page, then manually fix the torn bit value.The second step is checks the last operation to be done on that page (the m_lsn value).RgdsEka S.God didn't do this, Anna, WE did.— Robert Neville in I am Legend. |
|
|
|
|
|