Hello,
Someone came to me and asked me to restore a record, deleted by acident via
an ERP program. Problem is how do we restore only his record without
touching integrity of other peoples record. There are more then 20 table
involved when record is created or deleted.
MCWell I would restore the latest backup of the database to a dev enviornment
and locate that one record, then linked togeather all the information about
that record from each table and go from there to determine what can be
restored. It makes a difference on the type of data that was stored about
the record.. if that record is just a single entry or it it has several
detailed entries in a log table about that records activity in the database.
"CAMC1" wrote:
> Hello,
> Someone came to me and asked me to restore a record, deleted by acident vi
a
> an ERP program. Problem is how do we restore only his record without
> touching integrity of other peoples record. There are more then 20 table
> involved when record is created or deleted.
> MC
>
>|||That is what I tought.
I told the user that it is faster to re-create the record via his
application the restoring 1 user transaction.
MC
"JosephPruiett" <JosephPruiett@.discussions.microsoft.com> wrote in message
news:A36EF0B2-03E8-476D-A8FD-AC867228C453@.microsoft.com...
> Well I would restore the latest backup of the database to a dev
enviornment
> and locate that one record, then linked togeather all the information
about
> that record from each table and go from there to determine what can be
> restored. It makes a difference on the type of data that was stored about
> the record.. if that record is just a single entry or it it has several
> detailed entries in a log table about that records activity in the
database.[vbcol=seagreen]
>
> "CAMC1" wrote:
>
via[vbcol=seagreen]|||ABSOLUTELY!!!
Good way to handle it! It's rarely cost effective to restore just a small
amount of data.
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"CAMC1" <webmaster@.ozoptics.com> wrote in message
news:%23IEvOoDrGHA.3380@.TK2MSFTNGP04.phx.gbl...
> That is what I tought.
> I told the user that it is faster to re-create the record via his
> application the restoring 1 user transaction.
> MC
> "JosephPruiett" <JosephPruiett@.discussions.microsoft.com> wrote in message
> news:A36EF0B2-03E8-476D-A8FD-AC867228C453@.microsoft.com...
> enviornment
> about
> database.
> via
>|||Thanks
MC
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:ecgEBzDrGHA.4032@.TK2MSFTNGP03.phx.gbl...
> ABSOLUTELY!!!
> Good way to handle it! It's rarely cost effective to restore just a small
> amount of data.
> --
> Arnie Rowland
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "CAMC1" <webmaster@.ozoptics.com> wrote in message
> news:%23IEvOoDrGHA.3380@.TK2MSFTNGP04.phx.gbl...
message[vbcol=seagreen]
acident[vbcol=seagreen]
>|||"CAMC1" <webmaster@.ozoptics.com> wrote in message
news:%23IEvOoDrGHA.3380@.TK2MSFTNGP04.phx.gbl...
> That is what I tought.
> I told the user that it is faster to re-create the record via his
> application the restoring 1 user transaction.
You forgot the "AND NEVER DO THAT AGAIN!" part. :-)
> MC
> "JosephPruiett" <JosephPruiett@.discussions.microsoft.com> wrote in message
> news:A36EF0B2-03E8-476D-A8FD-AC867228C453@.microsoft.com...
> enviornment
> about
about[vbcol=seagreen]
> database.
acident[vbcol=seagreen]
> via
table[vbcol=seagreen]
>
No comments:
Post a Comment