December 29, 2008 at 5:46 am
Hi
By mistake we replace the actual data with old data by using sql import / export. Unfortunately we dont have the backup also. Is there anyway we can recover the actual data. Please help on this.
Prasad
December 29, 2008 at 5:58 am
If the database is important, why you dont have a backup policy in place?
Without a full backup + log backup chains i dont think you can restore to point in time....
What's the recovery model of your database?
December 29, 2008 at 6:16 am
Its happened by mistake and forgot to implement the backup policy. We have the full recovery model .
December 29, 2008 at 6:24 am
prasad (12/29/2008)
Its happened by mistake and forgot to implement the backup policy. We have the full recovery model .
Well that's the costliest mistake a DBA can make. I dont think you can recover that data from conventional methods as u dont have the backup. May be some third party tools can help you in that.... eg.. Lumigent's Log explorer...
December 29, 2008 at 7:54 am
prasad (12/29/2008)
By mistake we replace the actual data with old data by using sql import / export. Unfortunately we dont have the backup also. Is there anyway we can recover the actual data.
If you have absolutely no backups, then no. There is no way to get the data back. Even a log reader won't help since, without a full backup, the log will be auto-truncating on a regular basis.
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
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply