826
General Software Discussion / Re: recover an SQL .mdf file that is currently written to a bad sector
« Last post by Stoic Joker on June 23, 2015, 07:24 AM »Okay, this bit is marginally insane...but the sensible options appear to have been exhausted.. It seems that the db is attesting to be both valid and corrupt at the same time. I say this once before with a db that hadn't been properly maintained for a few years, and had some of it's slack space on a bad sector.
Probably best to hear from Shades before trying this, but...
If you run the MSSQL maintenance routine (Shrink database/files) on the db to compact the db it may allow you to get the actual data "out" while leaving the (presumed) corrupt slack space where it is.
It's a dangerous, and quite possibly insane idea. But if the current instance of SQL is indeed the only thing that can read the db, then maybe it can be leveraged (e.g. tricked into) copying the db for you.
Shades??
Probably best to hear from Shades before trying this, but...
If you run the MSSQL maintenance routine (Shrink database/files) on the db to compact the db it may allow you to get the actual data "out" while leaving the (presumed) corrupt slack space where it is.
It's a dangerous, and quite possibly insane idea. But if the current instance of SQL is indeed the only thing that can read the db, then maybe it can be leveraged (e.g. tricked into) copying the db for you.
Shades??

Recent Posts
