October 17, 2012 at 2:23 am
I'm a newbie and I'm using using SQL 2008 R2
I have a 10GB .bak file that when I restore requires 41GB. The restore fails because I currently have insufficient disk space. I don't understand, because the original MTB file is only 12GB. The Log file is 60GB (if that's of any consequence). Can I crop the .bak file before I restore?
October 17, 2012 at 2:30 am
sean 1516 (10/17/2012)
I'm a newbie and I'm using using SQL 2008 R2I have a 10GB .bak file that when I restore requires 41GB. The restore fails because I currently have insufficient disk space. I don't understand, because the original MTB file is only 12GB. The Log file is 60GB (if that's of any consequence). Can I crop the .bak file before I restore?
You need to shrink the database before taking the backup. Other wise it will try to create the db with same size as the original databse
October 17, 2012 at 3:06 am
When restoring SQL recreates the DB exactly as it was at time of backup, including file sizes. So you will need space for the full size of the original DB.
That the log is way bigger than the data file suggests missing log maintenance. Please read through this - Managing Transaction Logs[/url]
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
October 23, 2012 at 6:50 am
joeroshan (10/17/2012)
You need to shrink the database before taking the backup. Other wise it will try to create the db with same size as the original databse
joeroshan, hope you can suggest him to do a log backup rather than shrinking the log file.
Regards
Durai Nagarajan
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply