Hi,
Can anyone help me with this error?
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RVHS_database.mdf'.
What should i do to recover my database? Please help me outuse DBCC CHECKDB (use NOINDEX first; id an index is corrrupted it won't be a problem), then try REPAIR_FAST or REPAIR_REBUILD (it's time consuming) - see Books Online for more
Originally posted by Bluetooth
Hi,
Can anyone help me with this error?
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x0000000f3e4000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\RVHS_database.mdf'.
What should i do to recover my database? Please help me out|||ooops, I don't think the recommended switches will do the trick. It
's REPAIR_ALLOW_DATA_LOSS that will fix page allocation errors (which is what you have here). Do it within a transaction and don't commit untill you see what repairs are done and what errors got fixed.
Monday, March 26, 2012
I/O error (bad page ID) detected during read at offset 0x0000000f3e4000
Labels:
0x0000000f3e4000,
0x80004005,
database,
detected,
drivers,
driversql,
error,
errormicrosoft,
microsoft,
microsoftodbc,
mysql,
odbc,
offset,
ole,
oracle,
page,
provider,
server,
serveri,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment