Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
khermann
Starting Member
10 Posts |
 Posted - 2009-12-09 : 20:43:17
|
| I try to pre-allocate my MDF and LDF's to the 'as large as reasonable' to prevent auto-growth during production hours. In highly controlled environments we like to turn off auto-growth all together and manage this activity manually.I thought there was a way to handle my problem with the RESTORE command but I am mistaken. The problem I am having is this, using the following scenario:1. My data is 50GB in a 100GB file that i set the initial size to as 100GB.2. I backup the database, mybackup.bak3. I want to restore the database to a system but it only has 75GB of free space; I can't do this because the 100GB initial size set I am told there is not enough disk space for the restore, when i really only have 50GB of data.There must be a way to accomplish this without having to alter my production instance or shrinking files prior to taking a backup. I could have sworn I've done this in the past, so I'm feeling a bit dim - what am I missing?Thanks very muchkp.s. sql2005 sp3 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
khermann
Starting Member
10 Posts |
Posted - 2009-12-10 : 14:49:10
|
| I appreciate the quick response. I was afraid that would be the answer. Thanks again. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
Allocating file space best practice vs. restores