Database Recovery

We are trying to recover a database that has been
corrupted. We have a full backup with recovery from the
night before the problem, and one right after the problem
occurred. We did not do a Transaction Log backup. Will
this work:
1. Restore the second backup.
2. Do a Transaction Log backup - this should be all the
transactions since our 1st good backup (but it seems as
though the t-log is truncated during recovery because we
are getting an error when we try to apply it).
3. Restore the first backup.
4. Apply the Transaction log.
If the t-log is indeed truncated (why would it even allow
that?) do we have any way to recover those transactions?I don't think that will work. The correct course of action would have been
:-
Midnight - Full Backup
Hourly - Log Backups
13:30 User corrupts data.
13:33 Take Log Backup
Restore Full Database backup
Restore each hourly Log Backup in order
Restore from 13:33 Log Backup with the STOPAT clause set to 13:29
--
HTH
Ryan Waight, MCDBA, MCSE
"Ed" <anonymous@.discussions.microsoft.com> wrote in message
news:002901c3b29d$90932d80$a101280a@.phx.gbl...
> We are trying to recover a database that has been
> corrupted. We have a full backup with recovery from the
> night before the problem, and one right after the problem
> occurred. We did not do a Transaction Log backup. Will
> this work:
> 1. Restore the second backup.
> 2. Do a Transaction Log backup - this should be all the
> transactions since our 1st good backup (but it seems as
> though the t-log is truncated during recovery because we
> are getting an error when we try to apply it).
> 3. Restore the first backup.
> 4. Apply the Transaction log.
> If the t-log is indeed truncated (why would it even allow
> that?) do we have any way to recover those transactions?|||Should also mention that when we try the scenario below -
we get a 4305 error when we try to apply the transaction
log - I am assuming that is because the log is truncated -
or is there something else happening?
>--Original Message--
>We are trying to recover a database that has been
>corrupted. We have a full backup with recovery from the
>night before the problem, and one right after the
problem
>occurred. We did not do a Transaction Log backup. Will
>this work:
>1. Restore the second backup.
>2. Do a Transaction Log backup - this should be all the
>transactions since our 1st good backup (but it seems as
>though the t-log is truncated during recovery because we
>are getting an error when we try to apply it).
>3. Restore the first backup.
>4. Apply the Transaction log.
>If the t-log is indeed truncated (why would it even
allow
>that?) do we have any way to recover those transactions?
>.
>|||If you never did a log backup, you will only have the db backup to work with.
If the database is in simple recovery mode, the log is truncated regularly.
And even if the database is in full recovery mode, the log is truncated at 70% fill until you do the
first database backup.
So, chances that the log records are available to produce a usable log backup are slim to nothing.
If you like to try that, you would have to do the log backup before doing any type of restore.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Ed" <anonymous@.discussions.microsoft.com> wrote in message
news:002901c3b29d$90932d80$a101280a@.phx.gbl...
> We are trying to recover a database that has been
> corrupted. We have a full backup with recovery from the
> night before the problem, and one right after the problem
> occurred. We did not do a Transaction Log backup. Will
> this work:
> 1. Restore the second backup.
> 2. Do a Transaction Log backup - this should be all the
> transactions since our 1st good backup (but it seems as
> though the t-log is truncated during recovery because we
> are getting an error when we try to apply it).
> 3. Restore the first backup.
> 4. Apply the Transaction log.
> If the t-log is indeed truncated (why would it even allow
> that?) do we have any way to recover those transactions?