December 4, 2007 at 5:24 am
hi all !
i'm new here!
sorry about my bad english....
here is my problem:
i have hard disk that had errors on many files from disk...
the database files (MDF , LDF) were affected by HD errors too...
after repairing the errors with scan disk, the db became unuasble...it couldn't be opened by microsoft sql management studio, and the software that uses it....
i found a tool in internet (kernel sql database recover) but it's demo only , and the full version costs $399...
so, i ask if you can find out for any other solutions about the recovering...i saw that it's possible, because that tool opens the DB but shows only 5000 records and can't save...
i'm thankful for the attention...
sorry about my bad english....
TITLE: Microsoft SQL Server Management Studio
------------------------------
An error occurred when attaching the database(s). Click the hyperlink in the Message column for details.
------------------------------
BUTTONS:
OK
------------------------------
December 4, 2007 at 2:00 pm
I'll ask the obvious - was the database being backed up? And was the backup (or a copy of it) on media (disk, tape, whatever) that was not affected by your disk error?
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
December 5, 2007 at 12:49 am
hehe..... if it was backed up, should i ask this kind of questions here 😉
no...it doesn't have backup. 🙁
but there's a tool...strange kind of tool, that opens the base and it's readble, but it doesn't support SAVE because it's just demo version...
i was thinking that if that tool can open the base, it could be somewhere other tool that can open the base, too... 🙂
of course - i'm not 100% sure about that, but i made a large search over internet, and i found one, but it crashes at 14-15%.... "Recovery for Project server"...
i know that it's stupid that i don't have backup...but.... 🙁
any ideas ?
December 5, 2007 at 10:53 am
What error do you get if you try to manually attach the database?
Your best bet is probably to hack the database back into the server (create a dummy database of exactly the same name with the same files and file sizes - shutdown and swap in the damaged database), then set the database into EMERGENCY mode and run the EMERGENCY mode repair I put into CHECKDB in SS2005. That should be able to fix everything that's broken but you will have lost data plus the integrity of the business relationships inherent in the database.
And get a backup strategy.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
December 18, 2007 at 4:15 pm
Have you tried DBCC Repair/Rebuild or DBCC repair with data loss?
More Info:
http://msdn2.microsoft.com/en-us/library/aa258278(SQL.80).aspx
You need to determine what level of data loss is acceptable and then design a backup strategy to conform to your need. As you have found out, it is very easy for an unforseen event to trip you up. It is always best to be prepared.
As I like to say "Live and Learn"
December 19, 2007 at 4:19 am
BTW you can read Pauls totally excellent article on recovering corrupt database here
CodeMinkey
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply