Database backup

hi,
I took backup of the database and restored in some other location say mirror
database.
In the mirror database, I add some constraints by eliminating duplicates and
foreign key constraints.
In the meantime some data would have been updated or inserted inside the
original database.
How to identify the updated or inserted records without using triggeres. I
am also not allowed to add timestamp column to the structure.
pls help me to solve this.
thanks in advance
regds
vanithaVanitha
Take Transaction log backup with no truncate option from the main server
and apply it in the second server.
However, If you have made any changes to DML in the new database( as you
said constraint etc) then it may not possible.In those circumstances you are
left with no other option but to compare values table by table.
--
Regards
R.D
--Knowledge gets doubled when shared
"vanitha" wrote:

> hi,
> I took backup of the database and restored in some other location say mirr
or
> database.
> In the mirror database, I add some constraints by eliminating duplicates a
nd
> foreign key constraints.
> In the meantime some data would have been updated or inserted inside the
> original database.
> How to identify the updated or inserted records without using triggeres. I
> am also not allowed to add timestamp column to the structure.
> pls help me to solve this.
> thanks in advance
> regds
> vanitha
>|||If you're preparing a new database model be sure to test it well before you
deploy it into production.
For a final migration of data from the old database into the new one it
would seem in your case that the old system should be made inaccessible to
users for the duration of the migration process.
What exactly are you trying to acomplish?
ML|||no the production db will not go offline.
after applying constraints I will make the mirror db as the production db.
In the meantime I shd find the updated record and update that records also.
downtime for the production db will be only 1 hr.
thanks
vanitha
"ML" wrote:

> If you're preparing a new database model be sure to test it well before yo
u
> deploy it into production.
> For a final migration of data from the old database into the new one it
> would seem in your case that the old system should be made inaccessible to
> users for the duration of the migration process.
> What exactly are you trying to acomplish?
>
> ML|||there are millions of records so i can't chk record by record.
"R.D" wrote:
> Vanitha
> Take Transaction log backup with no truncate option from the main server
> and apply it in the second server.
> However, If you have made any changes to DML in the new database( as you
> said constraint etc) then it may not possible.In those circumstances you a
re
> left with no other option but to compare values table by table.
> --
> Regards
> R.D
> --Knowledge gets doubled when shared
>
> "vanitha" wrote:
>sql