March 15, 2011 at 9:11 am
Hi,
I have a situation where many changes were made to a SQL Server database yesterday. A process this morning erased those changes. I could restore a backup from last night, but a few more changes were made this morning to the database.
So, in general, how could I keep all of the changes that are in the backup and not lose the new changes that were made this morning? Is there a best practice way to get both back?
Thanks,
Mike
Mike Scalise, PMP
https://www.michaelscalise.com
March 15, 2011 at 9:22 am
I dont think it will be possible to do this directly from the backups, as you made changes this morning that you don't want restored you will not be able to do a Point-in-time restore from the t-log as the chain will be broken.
If you have t-log backups , you could do a restore up until you made the changes this morning, this would mean you would lose the current work though.
You could also look at restoring the earlier version and running a compare tool against the current version to merge the differences in the tables. though depending on the type of changes this might be difficult
March 15, 2011 at 9:24 am
Mike
I don't think there's an easy way of doing this. One option is to restore last night's backup to a different server (or a different database on the same server) and then use a tool like SQL Compare to identify the differences between the restored database and the live database.
John
March 16, 2011 at 11:04 am
I would go with John's suggestion with one suggestion. If you are using a third party backup & restore tool, like Litespeed, you can do object restores. Which means you could restore the tables in question (or procs in question, etc.) to different names, then do whatever finagling you need to do in order to combine those changes.
You didn't say if these were data changes or code changes, so that's why I'm being so vague on the how-to.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply