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 |
|
john.burns
Posting Yak Master
100 Posts |
 Posted - 2006-10-27 : 15:44:17
|
| Does 2+ hours to restore a 21GB db seem epecially long?? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-10-27 : 16:44:45
|
| Yes it does, but it could be due to your hardware or the sizes of the MDF and LDF. SQL Server 2005 drastically improves restore times. Tara Kizer |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2006-10-28 : 03:04:53
|
| It will take longer, IME, if the target database does not pre-exist - SQL Server seems to take a while to acquire and, perhaps, pre-initialise the data space.Also if your LOG table is spectacularly big, but lets say empty, that will significantly add tot he restore time - so a 21GB backup file may actually be representing a much more massive MDF and LDF set if files - which have to be created and initialised before the restore starts.You should be able to see this by using "STATS = 1" in the Restore command (to show progress in 1% steps) - if there is a longer delay between the start and the first STATS display than each subsequent 1% step then I reckon that's the issue.Kristen |
|
|
|
|
|
|
Restore - Quick question