April 16, 2015 at 3:05 pm
Hi all,
We have repartioned a server (create a larger C-drive/system partition). It's about Windows Server 2003. Before repartioning SP2 was not installed. After repartioning checkdisk started automatically (as normal after using a disk partitioning tool). Checkdisk did some interesting and bad things with my files: changing file permissions and make some files corrupt, how I don't know. Something to do with SP2 not installed and the NTFS filesystem. After this action I have a corrupted SQL database. Tried to repair with the DBCC CHECKDB repair commands, but fail. Error in event viewer:
Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x0000003bdc4000 in file 'D:\program files\Microsoft SQL Server\MSSQL\Data\352.MDF'.
I also still have NTFS errors in my event viewer. What to do? How can I repair the database? Only running checkdisk again? (and will this work?) Than all file security will be reset to Administrators.
Other ways to rebuild my database? (tools???) Unfortunally there isn't a good backup available due to a lack of good configuration of the backup software.
Could please someone help me out?
April 17, 2015 at 3:00 am
If the CheckDB repair is failing and you have no clean backup (Why oh why oh why????), then there's pretty much no option left. I hope the DB's not too important (I assume not too important since backups were not a priority)
Please run the following and post the full and complete output
DBCC CheckDB (<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
You may also want to notify the business owners of this database that there will be downtime, data loss and possibly worse.
To confirm, this is a SQL Server 2000 database?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 19, 2015 at 8:32 pm
-Try to import the data inside a new database file.
-Checked those database files in your MS Access program.
-May be there is a problem with your clients' program.
-Open those database files in some other MS Access.
In case actions on above don’t work in your situation, see more resources, which might be effective here
http://www.filerepairforum.com/forum/microsoft/microsoft-aa/access/1420-ms-access-corrupt-database - where you may know more about actions after corruption ms access database
https://access.recoverytoolbox.com/%5B/url%5D - paid solution, which is represented by Recovery Toolbox for Access, but if nothing works, it can become the proper and unique decision.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply