<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 Administration
»
Restore space needed WAY more than bak file...
Restore space needed WAY more than bak file size
Rate Topic
Display Mode
Topic Options
Author
Message
peterjbassi
peterjbassi
Posted Monday, February 11, 2013 10:40 AM
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, February 12, 2013 5:19 AM
Points: 7,
Visits: 23
I have a 14GB uncompressed .bak file that I'm trying to restore to a new 20GB (20,000MB) database that I just created . When I run the restore it fails with the following error:
There is insufficient free space on disk volume 'F:\' to create the database. The database requires 236339200000 additional free bytes, while only 198730047488 bytes are available.
Unless my math is off, 14GB is less than ~220-230GB. (The stated available bytes left on the disk is correct though). Anybody know what could be causing this? Thanks.
--------------------------------------------------------------
"Daterbase, taterbase, gatorbase."
Post #1418556
Bill (fluffydeadangel)
Bill (fluffydeadangel)
Posted Monday, February 11, 2013 10:43 AM
Valued Member
Group: General Forum Members
Last Login: Today @ 9:05 AM
Points: 70,
Visits: 220
My understanding is that even uncompressed backups do not backup "Free space". so where ever this bak came from... check the actual mdf/ndf file sizes. the space used data space can be 14GB and still have 250GB of "free space" that will be restored on .. .well restore.
Please someone correct me if this statement is wrong.
Post #1418558
Bill (fluffydeadangel)
Bill (fluffydeadangel)
Posted Monday, February 11, 2013 10:46 AM
Valued Member
Group: General Forum Members
Last Login: Today @ 9:05 AM
Points: 70,
Visits: 220
http://www.sqlservercentral.com/Forums/Topic777462-169-1.aspx
This is a previous link that has this exact same issue.
Post #1418562
peterjbassi
peterjbassi
Posted Monday, February 11, 2013 10:53 AM
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, February 12, 2013 5:19 AM
Points: 7,
Visits: 23
Thanks Bill. That's exactly what I was looking for. Sorry for the repost.
--------------------------------------------------------------
"Daterbase, taterbase, gatorbase."
Post #1418564
Bill (fluffydeadangel)
Bill (fluffydeadangel)
Posted Monday, February 11, 2013 11:01 AM
Valued Member
Group: General Forum Members
Last Login: Today @ 9:05 AM
Points: 70,
Visits: 220
No worries. They can get lost in time. Glad to help ^.^
Post #1418572
Jeff Moden
Jeff Moden
Posted Monday, February 11, 2013 3:31 PM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 1:51 PM
Points: 32,906,
Visits: 26,789
As a sidebar, I'm thinking there's something seriously wrong with the database. You're talking about a very small database using almost a quarter of a Terabyte! When you finally get this bugger loaded, look at the recovery model. I'd bet credits to Navy beans that it's in the FULL or Bulk Logged recovery model and that no one has taken a transactional log backup for MONTHS.
--Jeff Moden
"
RBAR
is pronounced "ree-bar" and is a "Modenism" for "
R
ow-
B
y-
A
gonizing-
R
ow".
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Post #1418665
Gazareth
Gazareth
Posted Tuesday, February 12, 2013 5:15 AM
UDP Broadcaster
Group: General Forum Members
Last Login: Yesterday @ 1:53 AM
Points: 1,474,
Visits: 2,342
Jeff Moden (2/11/2013)
As a sidebar, I'm thinking there's something seriously wrong with the database. You're talking about a very small database using almost a quarter of a Terabyte! When you finally get this bugger loaded, look at the recovery model. I'd bet credits to Navy beans that it's in the FULL or Bulk Logged recovery model and that no one has taken a transactional log backup for MONTHS.
I had a similar problem recently - the culprit was an autogrow setting that been set to 1,000... percent.
Post #1418890
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
