jeff.mason (10/15/2010)
PaulB-TheOneAndOnly (10/15/2010)
Steve Jones - SSC Editor (10/15/2010)
I would have thought so, but if people entered data in a new system, you can't restore without losing that data. So you need to migrate backwards the data.or... you can perhaps
1- Detach affected database
2- Move affected database datafiles to a different location
3- Attach affected database as bad_db
4- Restore db point-in-time until the moment of the tragic event.
5- Add "good" data from bad_db into restored db
Isn't that another way of saying the same thing?
Don't think so.
So far I've heard about rolling out bad data while keeping good data until reaching the point where database was kosher.
Proposed approach is to start with a kosher database then add "good" data generated after the "tragic event". 😉
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.