On Thu, 31 Jul 2008 11:45:15 +0100, Jim wrote:
>I'm guessing the answer is 'no', but I thought I'd ask. Basically we have a
client where it looks like someone has issued a DROP TABLE command - or at
least so far as we can tell. The table certainly isn't there.
No backups, of course. That would be _too_ easy.
MSSQL2000 (actually MSDE).
Any thoughts appreciated.
Jim
Hi Jim,
The simple answer is, indeed, 'no'.
But there might still be *some* hope.
If the DROP TABLE was executed from within a transaction and that
transaction has not yet been committed, you can roll it back. But I
guess that this is not the case here. :)
Which means that only one hope remains - purchase a third-party product
(or download a trial version) that is able to read the log file and
reconstuct the table from that information. Whether this succeeds
depends on the recovery model used for the database, but it's always
worth a shot.
Well-known third-party programs that are able to read and decode the SQL
Server log are:
* Red Gate's SQL Log Rescue
http://www.red-gate.com/products/SQL...scue/index.htm
* Lumigent Log Explorer for SQL Server
http://www.lumigent.com/products/log_explorer.html
* ApexSQL Log
http://www.apexsql.com/sql_tools_log.asp
--
Hugo Kornelis, SQL Server MVP
My SQL Server blog:
http://sqlblog.com/blogs/hugo_kornelis