May 22, 2018 at 9:26 am
I'm starting this as general discussion to get different ideas on what everyone does. We currently use LiteSpeed for our backups solely for the reason it allows object level restores. So if a table is accidentally updated or deleted then we can restore just that table instead of having to restore the entire database and bringing over the table after that. This is important because it is not only quicker, but also more practical given that we do not have enough free space to restore some of our larger databases while keeping all existing around. The issue is that native SQL backups are becoming the standard across different groups in the organization as well as trying to eliminate the extra costs associated with the licensing of LiteSpeed. Does anyone have any alternatives to this? How would you handle restoring only one table in a database that is, for example, 350 GB and has a backup of 55 GB?
May 22, 2018 at 11:36 am
you can achieve this if you design system using one table per database, it is crazy thou, good luck 🙂
you can also bcp out each table.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply