March 3, 2015 at 8:48 am
Guys,
I have a new production database to deploy; It is an extract of a little bit of data from an existing database and was created by restoring the original, truncating some of the tables and then copying the required data back in from the source database.
Currently the source database takes about 5 hours to restore. The new database is NEVER going to get to the size of the original (well maybe in 15 years or so..). Can I make the backup/restore faster by shrinking the database first.
I don't want a tirade of don't shrink the database responses 🙂 these are very specific circumstances: I need to be able to restore quickly if one of the migration stages goes belly up - I don't want to be waiting 5 hours to backup and then 5 hours to restore.
March 3, 2015 at 8:57 am
Shrinking the database in this case is ok: you need it, do it.
Backups do not copy empty pages, so the backup process itself will not be any faster.
If you need faster backups/restores you have some options:
* compress it (works also in standard edition)
* use a different backup strategy (filegroup backups for instance)
-- Gianluca Sartori
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply