September 24, 2009 at 4:30 am
Friends,
I have been using a third party toll that offers excellent object level recovery from the compressed backup file, whereby individual tables can easily be restored from the latest available backup file.
I can find that by default SQL2008 itself offers compression technique which is actually more better than the current tool am using. But any idea if SQL2008 offers the same object level recovery technique or any alternate method by which the tables can be restored easily from the backup file without creating temporary databases and transferring db through SSIS.
Thanks
Eben
September 24, 2009 at 4:54 am
Third party tools are normally used, Object level restores are not supported in sql server yet.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
September 29, 2009 at 6:24 am
Hi,
Thanks for the info
May 22, 2013 at 12:25 pm
Resurrecting this thread with a question I have...
Can someone explain why SQL Server doesn't support object level recovery in a native manner?
How do 3rd party vendors make this possible?
I'm just looking for general knowledge here.
Thanks!
May 22, 2013 at 1:57 pm
AmarettoSlim (5/22/2013)
Resurrecting this thread with a question I have...Can someone explain why SQL Server doesn't support object level recovery in a native manner?
How do 3rd party vendors make this possible?
I'm just looking for general knowledge here.
Thanks!
the 3rd part apps read the transaction log and/or full backup, and compare it to your current object(s);
from there the 3rd party application can produce the appropriate insert/update/delete statements based on comparing the two objects), sometimes by creating a script based on the log changes, sometimes based on just comparing values.
While technically no different than you restoring a backup, and comparing two tables yourself, and generating the appropriate scripts based on your own analysis, such third party tools can save you enormous amounts of time you'd spend on analysis and scripting out the changes, assuming you have a backup strategy in place before the data gets stepped on and needs to be restored.
Lowell
May 22, 2013 at 3:04 pm
AmarettoSlim (5/22/2013)
Can someone explain why SQL Server doesn't support object level recovery in a native manner?
Because doing so would allow a native restore to result in a transactionally inconsistent database (imagine restoring the Client table and Invoices tables but not the Sales table, could mean that afterwards a client has an invoice for items that are not recorded as sold.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 23, 2013 at 2:41 am
Maybe SQL12 will steal flashback 😮
Dird
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply