Hi Everyone,I'm looking to buy one or more recovery tool software, but it's very difficulty to find real world experiences on the internet.Most of the 'tips' are from the manufacturers, advertising on forums as fake users/specialists.The rest are just resulted from some googling and grabbing the first results links.Thats's not what I'm looking for.I want you (fellows, experts, MVPs, MCM), to share your personal real world experiencies with low level 3rd party recovery software, to be used on those situatons where everything else was tried and failed (including emergency mode, DBCC CHECKDB/CHECKTABLE REPAIR_ALLOW_DATA_LOSS, and so on).DBCC is a very limited tool and when we didn't have any alternative options left, something recovered / partial recovery may be better than nothing.There are many situations where one of the last rows of a critical system table (like sysrscols) gets corrupted in a large database.So most of your database could be saved.Other times, the size of the database files, for some odd reason are different on the metadata and on the disk, so SQL Server continues to read the file after the end of the file and aborts the connection.This is something that could be fixed (the metadata information) and a good tool, should report any orphan allocation on metadata, beyond that point, giving us the option to accept that kind os data loss and fix it !More than that, its very likely that the information on the page header of the actual data page is intact, so an incorret metadata about allocation could be corrected, even in that chaotic situation.But I didn't found a tool with this kind of simple logic, but precise/detailed error reporting.Most of them just prints how many rows were successfully read from each table with no reports, on what was wrong, what was fixed, what was lost, and so on (like DBCC actually does on many situations).This kind of report can make us confident and able to agree an acceptable level of loss with the user or the client.Bad experiences with some marketed tools are very useful too.If we don't know what to buy, information on what TO DO NOT Buy is better than nothing.Links to articles about unsupported system tables fixing/editing, using Dedicated Administration Connection, allowing updates on system tables,... and so on, are also very welcome.Please no discussion or warnings. I'm aware about the risks, but as I told you before, I'm looking for solutions to exceptional situations where everything else was tried.I'm sure it will help many of us.No advertising, please !
↧