Dear all,
if i delete a row in a table accidently , how can i recover that rows
in case 1: just delete it a few second before
in case 2: delete it and add several rows after deleted rowsSQL Server doesn't provided a 'undelete' method. You will have to read the
transaction log using commands like DBCC LOG, or fn_dblog. But there isn't
much official documentation available about these commands. Another
alternative is to use a tool like Lumigent Log Explorer that can recover
data from the transaction log, as long as that transaction is in the
transaction log.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:CF2DC4B2-3CB8-47BA-B200-E91D03890E07@.microsoft.com...
Dear all,
if i delete a row in a table accidently , how can i recover that rows
in case 1: just delete it a few second before
in case 2: delete it and add several rows after deleted rows|||> Dear all,
> if i delete a row in a table accidently , how can i recover that rows
> in case 1: just delete it a few second before
> in case 2: delete it and add several rows after deleted rows
Backup is your friend here.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com|||Joe
Vyas has already answered your question.
I'd like to add if do soem testing (delete,insert,update) on QA add BEGIN
TRAN before a statement and make sure that you did right thing and then
COMMIT
BEGIN TRAN
delete from Table
10000000 (rows) affected
Mistake!!!!!!!!!!!!!!!!!!!
Rollback Tran
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:CF2DC4B2-3CB8-47BA-B200-E91D03890E07@.microsoft.com...
> Dear all,
> if i delete a row in a table accidently , how can i recover that rows
> in case 1: just delete it a few second before
> in case 2: delete it and add several rows after deleted rows|||Recovery is not a method if there have some rows added after the row is
deleted!|||If you had a backup, then you could at least restore it as a different
database, and selectively copy the required rows back into your database.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:2D3C1228-60E5-4326-A55E-DF964EA474BD@.microsoft.com...
Recovery is not a method if there have some rows added after the row is
deleted!|||Hi Joe
>if i delete a row in a table accidently , how can i recover that rows
Accidents can ONLY be prevented with precautions.
You can write a trigger to avoid deletion using @.@.rowcount, if you dont have
regular deletions. You can use this to specific user also.
If you find that official regular deletions are inevitable(practically true)
use triggers to add to to history tables so that you can easily retrieve the
row you want.
Regards
R.D
"Narayana Vyas Kondreddi" wrote:
> If you had a backup, then you could at least restore it as a different
> database, and selectively copy the required rows back into your database.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:2D3C1228-60E5-4326-A55E-DF964EA474BD@.microsoft.com...
> Recovery is not a method if there have some rows added after the row is
> deleted!
>
>
Showing posts with label accidently. Show all posts
Showing posts with label accidently. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
Recovering dropped SQL database
I am in a big trouble ,
accidently i have issued a DROP DATABASE XXX command in the sql client, thinking its a local server....... The whole 4 months of database database is now dropped.
Please help me , how can i recover the database ....
thanks in advance
If you don′t have a backup of the data, I will have to tell you, that there is no UNDO button for that. Sorry.HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.desql
Wednesday, March 21, 2012
Recover the data
Hi,
My appln runs on a remote server. A few minutes ago i accidently ran a
'Truncate table' command. Is there anyway to recover it thru Query Analyzer.
The DB Recovery model is SIMPLE and i have the dbOwner permission.
Thanking in Advance
LaraNo. Restore from the latest database backup or re-load the data. You can try
any of the log reading
tools (I've listed some on my links page), but the data is most probably not
in the log anymore
because of simple recovery mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Lara" <lara169@.gmail.com> wrote in message news:%23Pp%23vE$9FHA.3952@.TK2MSFTNGP09.phx.gbl.
.
> Hi,
> My appln runs on a remote server. A few minutes ago i accidently ran a 'Tr
uncate table' command.
> Is there anyway to recover it thru Query Analyzer. The DB Recovery model i
s SIMPLE and i have the
> dbOwner permission.
> Thanking in Advance
> Lara
>|||Thanks
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uqaa3U$9FHA.1996@.TK2MSFTNGP10.phx.gbl...
> No. Restore from the latest database backup or re-load the data. You can
> try any of the log reading tools (I've listed some on my links page), but
> the data is most probably not in the log anymore because of simple
> recovery mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Lara" <lara169@.gmail.com> wrote in message
> news:%23Pp%23vE$9FHA.3952@.TK2MSFTNGP09.phx.gbl...
>
My appln runs on a remote server. A few minutes ago i accidently ran a
'Truncate table' command. Is there anyway to recover it thru Query Analyzer.
The DB Recovery model is SIMPLE and i have the dbOwner permission.
Thanking in Advance
LaraNo. Restore from the latest database backup or re-load the data. You can try
any of the log reading
tools (I've listed some on my links page), but the data is most probably not
in the log anymore
because of simple recovery mode.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Lara" <lara169@.gmail.com> wrote in message news:%23Pp%23vE$9FHA.3952@.TK2MSFTNGP09.phx.gbl.
.
> Hi,
> My appln runs on a remote server. A few minutes ago i accidently ran a 'Tr
uncate table' command.
> Is there anyway to recover it thru Query Analyzer. The DB Recovery model i
s SIMPLE and i have the
> dbOwner permission.
> Thanking in Advance
> Lara
>|||Thanks
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uqaa3U$9FHA.1996@.TK2MSFTNGP10.phx.gbl...
> No. Restore from the latest database backup or re-load the data. You can
> try any of the log reading tools (I've listed some on my links page), but
> the data is most probably not in the log anymore because of simple
> recovery mode.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Lara" <lara169@.gmail.com> wrote in message
> news:%23Pp%23vE$9FHA.3952@.TK2MSFTNGP09.phx.gbl...
>
Tuesday, March 20, 2012
Recover lost data after wrong backup restored
I have accidently restored a SQL database (using Force restore over existing
database in EM) using a backup which was 1 month older than the latest
backup, and have therefore lost some important data from the existing
database. Is there any way that I can recover the lost data?
Thanks for any help.Seen from SQL Server's viewpoint, the data has been physically overwritten.
Either hunt down a later backup, or see of there is any OS or possibly SAN l
evel utility that might
help you here (I wouldn't have much hope for this but think it is at least w
orth mentioning).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Williams" <johnwilliams_esquire@.NOhotmailSPAM.com> wrote in message
news:uSRIcb5rEHA.536@.TK2MSFTNGP11.phx.gbl...
>I have accidently restored a SQL database (using Force restore over existin
g
> database in EM) using a backup which was 1 month older than the latest
> backup, and have therefore lost some important data from the existing
> database. Is there any way that I can recover the lost data?
> Thanks for any help.
>
>
database in EM) using a backup which was 1 month older than the latest
backup, and have therefore lost some important data from the existing
database. Is there any way that I can recover the lost data?
Thanks for any help.Seen from SQL Server's viewpoint, the data has been physically overwritten.
Either hunt down a later backup, or see of there is any OS or possibly SAN l
evel utility that might
help you here (I wouldn't have much hope for this but think it is at least w
orth mentioning).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Williams" <johnwilliams_esquire@.NOhotmailSPAM.com> wrote in message
news:uSRIcb5rEHA.536@.TK2MSFTNGP11.phx.gbl...
>I have accidently restored a SQL database (using Force restore over existin
g
> database in EM) using a backup which was 1 month older than the latest
> backup, and have therefore lost some important data from the existing
> database. Is there any way that I can recover the lost data?
> Thanks for any help.
>
>
Recover lost data after wrong backup restored
I have accidently restored a SQL database (using Force restore over existing
database in EM) using a backup which was 1 month older than the latest
backup, and have therefore lost some important data from the existing
database. Is there any way that I can recover the lost data?
Thanks for any help.
Seen from SQL Server's viewpoint, the data has been physically overwritten.
Either hunt down a later backup, or see of there is any OS or possibly SAN level utility that might
help you here (I wouldn't have much hope for this but think it is at least worth mentioning).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Williams" <johnwilliams_esquire@.NOhotmailSPAM.com> wrote in message
news:uSRIcb5rEHA.536@.TK2MSFTNGP11.phx.gbl...
>I have accidently restored a SQL database (using Force restore over existing
> database in EM) using a backup which was 1 month older than the latest
> backup, and have therefore lost some important data from the existing
> database. Is there any way that I can recover the lost data?
> Thanks for any help.
>
>
database in EM) using a backup which was 1 month older than the latest
backup, and have therefore lost some important data from the existing
database. Is there any way that I can recover the lost data?
Thanks for any help.
Seen from SQL Server's viewpoint, the data has been physically overwritten.
Either hunt down a later backup, or see of there is any OS or possibly SAN level utility that might
help you here (I wouldn't have much hope for this but think it is at least worth mentioning).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Williams" <johnwilliams_esquire@.NOhotmailSPAM.com> wrote in message
news:uSRIcb5rEHA.536@.TK2MSFTNGP11.phx.gbl...
>I have accidently restored a SQL database (using Force restore over existing
> database in EM) using a backup which was 1 month older than the latest
> backup, and have therefore lost some important data from the existing
> database. Is there any way that I can recover the lost data?
> Thanks for any help.
>
>
Recover lost data after wrong backup restored
I have accidently restored a SQL database (using Force restore over existing
database in EM) using a backup which was 1 month older than the latest
backup, and have therefore lost some important data from the existing
database. Is there any way that I can recover the lost data?
Thanks for any help.Seen from SQL Server's viewpoint, the data has been physically overwritten.
Either hunt down a later backup, or see of there is any OS or possibly SAN level utility that might
help you here (I wouldn't have much hope for this but think it is at least worth mentioning).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Williams" <johnwilliams_esquire@.NOhotmailSPAM.com> wrote in message
news:uSRIcb5rEHA.536@.TK2MSFTNGP11.phx.gbl...
>I have accidently restored a SQL database (using Force restore over existing
> database in EM) using a backup which was 1 month older than the latest
> backup, and have therefore lost some important data from the existing
> database. Is there any way that I can recover the lost data?
> Thanks for any help.
>
>
database in EM) using a backup which was 1 month older than the latest
backup, and have therefore lost some important data from the existing
database. Is there any way that I can recover the lost data?
Thanks for any help.Seen from SQL Server's viewpoint, the data has been physically overwritten.
Either hunt down a later backup, or see of there is any OS or possibly SAN level utility that might
help you here (I wouldn't have much hope for this but think it is at least worth mentioning).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Williams" <johnwilliams_esquire@.NOhotmailSPAM.com> wrote in message
news:uSRIcb5rEHA.536@.TK2MSFTNGP11.phx.gbl...
>I have accidently restored a SQL database (using Force restore over existing
> database in EM) using a backup which was 1 month older than the latest
> backup, and have therefore lost some important data from the existing
> database. Is there any way that I can recover the lost data?
> Thanks for any help.
>
>
Recover from a nuked database
One of our apps has accidently nuked one of our live databases and for
some reason our last backup was 1 month ago
It will have done a drop schema then re-created the schema and added 2
test records
Is there any way of rolling back the database to the point before the
drop + create ?
The MDF and LDF are still the same size which means the logs are
intact
AdamWhat recovery model?
If simple, you are most probably toast.
If full, you might be able to do BACKUP LOG, then restore the most recent da
tabase backups and all
subsequent log backups where you specify STOPAT for the most recent log back
up. This assumes that
you have an unbroken chain of log records (didn't do things like BACKUP LOG
.. WITH TRUNCATE ONLY).
You could also check out some of the log reader tools and see if they can mi
ne out of the
transaction log, but of course they are totally dependent on the log records
being in the
transaction log.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Adam // Internetware" <internetware@.gmail.com> wrote in message
news:1184081055.300348.184120@.22g2000hsm.googlegroups.com...
> One of our apps has accidently nuked one of our live databases and for
> some reason our last backup was 1 month ago
> It will have done a drop schema then re-created the schema and added 2
> test records
> Is there any way of rolling back the database to the point before the
> drop + create ?
> The MDF and LDF are still the same size which means the logs are
> intact
> Adam
>|||On Jul 10, 4:31 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> What recovery model?
> If simple, you are most probably toast.
> If full, you might be able to do BACKUP LOG, then restore the most recent
database backups and all
> subsequent log backups where you specify STOPAT for the most recent log ba
ckup. This assumes that
> you have an unbroken chain of log records (didn't do things like BACKUP LO
G ... WITH TRUNCATE ONLY).
> You could also check out some of the log reader tools and see if they can
mine out of the
> transaction log, but of course they are totally dependent on the log recor
ds being in the
> transaction log.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> "Adam // Internetware" <internetw...@.gmail.com> wrote in messagenews:11840
81055.300348.184120@.22g2000hsm.googlegroups.com...
>
>
>
>
>
Looks like I'm Ok the Redgate log rescue seems to have picked up most
of the transaction log so I think I can rollback - give or take some
issues with FK's
Thx
Adam
some reason our last backup was 1 month ago
It will have done a drop schema then re-created the schema and added 2
test records
Is there any way of rolling back the database to the point before the
drop + create ?
The MDF and LDF are still the same size which means the logs are
intact
AdamWhat recovery model?
If simple, you are most probably toast.
If full, you might be able to do BACKUP LOG, then restore the most recent da
tabase backups and all
subsequent log backups where you specify STOPAT for the most recent log back
up. This assumes that
you have an unbroken chain of log records (didn't do things like BACKUP LOG
.. WITH TRUNCATE ONLY).
You could also check out some of the log reader tools and see if they can mi
ne out of the
transaction log, but of course they are totally dependent on the log records
being in the
transaction log.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Adam // Internetware" <internetware@.gmail.com> wrote in message
news:1184081055.300348.184120@.22g2000hsm.googlegroups.com...
> One of our apps has accidently nuked one of our live databases and for
> some reason our last backup was 1 month ago
> It will have done a drop schema then re-created the schema and added 2
> test records
> Is there any way of rolling back the database to the point before the
> drop + create ?
> The MDF and LDF are still the same size which means the logs are
> intact
> Adam
>|||On Jul 10, 4:31 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> What recovery model?
> If simple, you are most probably toast.
> If full, you might be able to do BACKUP LOG, then restore the most recent
database backups and all
> subsequent log backups where you specify STOPAT for the most recent log ba
ckup. This assumes that
> you have an unbroken chain of log records (didn't do things like BACKUP LO
G ... WITH TRUNCATE ONLY).
> You could also check out some of the log reader tools and see if they can
mine out of the
> transaction log, but of course they are totally dependent on the log recor
ds being in the
> transaction log.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph
ttp://sqlblog.com/blogs/tibor_karaszi
> "Adam // Internetware" <internetw...@.gmail.com> wrote in messagenews:11840
81055.300348.184120@.22g2000hsm.googlegroups.com...
>
>
>
>
>
Looks like I'm Ok the Redgate log rescue seems to have picked up most
of the transaction log so I think I can rollback - give or take some
issues with FK's
Thx
Adam
Recover from a nuked database
One of our apps has accidently nuked one of our live databases and for
some reason our last backup was 1 month ago
It will have done a drop schema then re-created the schema and added 2
test records
Is there any way of rolling back the database to the point before the
drop + create ?
The MDF and LDF are still the same size which means the logs are
intact
Adam
What recovery model?
If simple, you are most probably toast.
If full, you might be able to do BACKUP LOG, then restore the most recent database backups and all
subsequent log backups where you specify STOPAT for the most recent log backup. This assumes that
you have an unbroken chain of log records (didn't do things like BACKUP LOG ... WITH TRUNCATE ONLY).
You could also check out some of the log reader tools and see if they can mine out of the
transaction log, but of course they are totally dependent on the log records being in the
transaction log.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Adam // Internetware" <internetware@.gmail.com> wrote in message
news:1184081055.300348.184120@.22g2000hsm.googlegro ups.com...
> One of our apps has accidently nuked one of our live databases and for
> some reason our last backup was 1 month ago
> It will have done a drop schema then re-created the schema and added 2
> test records
> Is there any way of rolling back the database to the point before the
> drop + create ?
> The MDF and LDF are still the same size which means the logs are
> intact
> Adam
>
|||On Jul 10, 4:31 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> What recovery model?
> If simple, you are most probably toast.
> If full, you might be able to do BACKUP LOG, then restore the most recent database backups and all
> subsequent log backups where you specify STOPAT for the most recent log backup. This assumes that
> you have an unbroken chain of log records (didn't do things like BACKUP LOG ... WITH TRUNCATE ONLY).
> You could also check out some of the log reader tools and see if they can mine out of the
> transaction log, but of course they are totally dependent on the log records being in the
> transaction log.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Adam // Internetware" <internetw...@.gmail.com> wrote in messagenews:1184081055.300348.184120@.22g2000hsm.go oglegroups.com...
>
>
Looks like I'm Ok the Redgate log rescue seems to have picked up most
of the transaction log so I think I can rollback - give or take some
issues with FK's
Thx
Adam
some reason our last backup was 1 month ago
It will have done a drop schema then re-created the schema and added 2
test records
Is there any way of rolling back the database to the point before the
drop + create ?
The MDF and LDF are still the same size which means the logs are
intact
Adam
What recovery model?
If simple, you are most probably toast.
If full, you might be able to do BACKUP LOG, then restore the most recent database backups and all
subsequent log backups where you specify STOPAT for the most recent log backup. This assumes that
you have an unbroken chain of log records (didn't do things like BACKUP LOG ... WITH TRUNCATE ONLY).
You could also check out some of the log reader tools and see if they can mine out of the
transaction log, but of course they are totally dependent on the log records being in the
transaction log.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Adam // Internetware" <internetware@.gmail.com> wrote in message
news:1184081055.300348.184120@.22g2000hsm.googlegro ups.com...
> One of our apps has accidently nuked one of our live databases and for
> some reason our last backup was 1 month ago
> It will have done a drop schema then re-created the schema and added 2
> test records
> Is there any way of rolling back the database to the point before the
> drop + create ?
> The MDF and LDF are still the same size which means the logs are
> intact
> Adam
>
|||On Jul 10, 4:31 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:[vbcol=seagreen]
> What recovery model?
> If simple, you are most probably toast.
> If full, you might be able to do BACKUP LOG, then restore the most recent database backups and all
> subsequent log backups where you specify STOPAT for the most recent log backup. This assumes that
> you have an unbroken chain of log records (didn't do things like BACKUP LOG ... WITH TRUNCATE ONLY).
> You could also check out some of the log reader tools and see if they can mine out of the
> transaction log, but of course they are totally dependent on the log records being in the
> transaction log.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Adam // Internetware" <internetw...@.gmail.com> wrote in messagenews:1184081055.300348.184120@.22g2000hsm.go oglegroups.com...
>
>
Looks like I'm Ok the Redgate log rescue seems to have picked up most
of the transaction log so I think I can rollback - give or take some
issues with FK's
Thx
Adam
Recover from a nuked database
One of our apps has accidently nuked one of our live databases and for
some reason our last backup was 1 month ago
It will have done a drop schema then re-created the schema and added 2
test records
Is there any way of rolling back the database to the point before the
drop + create ?
The MDF and LDF are still the same size which means the logs are
intact
AdamWhat recovery model?
If simple, you are most probably toast.
If full, you might be able to do BACKUP LOG, then restore the most recent database backups and all
subsequent log backups where you specify STOPAT for the most recent log backup. This assumes that
you have an unbroken chain of log records (didn't do things like BACKUP LOG ... WITH TRUNCATE ONLY).
You could also check out some of the log reader tools and see if they can mine out of the
transaction log, but of course they are totally dependent on the log records being in the
transaction log.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Adam // Internetware" <internetware@.gmail.com> wrote in message
news:1184081055.300348.184120@.22g2000hsm.googlegroups.com...
> One of our apps has accidently nuked one of our live databases and for
> some reason our last backup was 1 month ago
> It will have done a drop schema then re-created the schema and added 2
> test records
> Is there any way of rolling back the database to the point before the
> drop + create ?
> The MDF and LDF are still the same size which means the logs are
> intact
> Adam
>|||On Jul 10, 4:31 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> What recovery model?
> If simple, you are most probably toast.
> If full, you might be able to do BACKUP LOG, then restore the most recent database backups and all
> subsequent log backups where you specify STOPAT for the most recent log backup. This assumes that
> you have an unbroken chain of log records (didn't do things like BACKUP LOG ... WITH TRUNCATE ONLY).
> You could also check out some of the log reader tools and see if they can mine out of the
> transaction log, but of course they are totally dependent on the log records being in the
> transaction log.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Adam // Internetware" <internetw...@.gmail.com> wrote in messagenews:1184081055.300348.184120@.22g2000hsm.googlegroups.com...
> > One of our apps has accidently nuked one of our live databases and for
> > some reason our last backup was 1 month ago
> > It will have done a drop schema then re-created the schema and added 2
> > test records
> > Is there any way of rolling back the database to the point before the
> > drop + create ?
> > The MDF and LDF are still the same size which means the logs are
> > intact
> > Adam
Looks like I'm Ok the Redgate log rescue seems to have picked up most
of the transaction log so I think I can rollback - give or take some
issues with FK's
Thx
Adam
some reason our last backup was 1 month ago
It will have done a drop schema then re-created the schema and added 2
test records
Is there any way of rolling back the database to the point before the
drop + create ?
The MDF and LDF are still the same size which means the logs are
intact
AdamWhat recovery model?
If simple, you are most probably toast.
If full, you might be able to do BACKUP LOG, then restore the most recent database backups and all
subsequent log backups where you specify STOPAT for the most recent log backup. This assumes that
you have an unbroken chain of log records (didn't do things like BACKUP LOG ... WITH TRUNCATE ONLY).
You could also check out some of the log reader tools and see if they can mine out of the
transaction log, but of course they are totally dependent on the log records being in the
transaction log.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Adam // Internetware" <internetware@.gmail.com> wrote in message
news:1184081055.300348.184120@.22g2000hsm.googlegroups.com...
> One of our apps has accidently nuked one of our live databases and for
> some reason our last backup was 1 month ago
> It will have done a drop schema then re-created the schema and added 2
> test records
> Is there any way of rolling back the database to the point before the
> drop + create ?
> The MDF and LDF are still the same size which means the logs are
> intact
> Adam
>|||On Jul 10, 4:31 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> What recovery model?
> If simple, you are most probably toast.
> If full, you might be able to do BACKUP LOG, then restore the most recent database backups and all
> subsequent log backups where you specify STOPAT for the most recent log backup. This assumes that
> you have an unbroken chain of log records (didn't do things like BACKUP LOG ... WITH TRUNCATE ONLY).
> You could also check out some of the log reader tools and see if they can mine out of the
> transaction log, but of course they are totally dependent on the log records being in the
> transaction log.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Adam // Internetware" <internetw...@.gmail.com> wrote in messagenews:1184081055.300348.184120@.22g2000hsm.googlegroups.com...
> > One of our apps has accidently nuked one of our live databases and for
> > some reason our last backup was 1 month ago
> > It will have done a drop schema then re-created the schema and added 2
> > test records
> > Is there any way of rolling back the database to the point before the
> > drop + create ?
> > The MDF and LDF are still the same size which means the logs are
> > intact
> > Adam
Looks like I'm Ok the Redgate log rescue seems to have picked up most
of the transaction log so I think I can rollback - give or take some
issues with FK's
Thx
Adam
Subscribe to:
Posts (Atom)