Timeline for Restoring with replace going incredibly quickly
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2013 at 23:17 | comment | added | Hannah Vernon♦ | 100GB is actually decently large - enough to take a substantial amount of time. I could see it taking on the order of 20 minutes or more, depending on the speed of your disk subsystem. | |
| Oct 29, 2013 at 22:53 | comment | added | Sean Long | The log files are actually only 100GB. I didn't measure them on the previous attempts, so that might be the difference. good catch. | |
| Oct 29, 2013 at 22:47 | comment | added | Hannah Vernon♦ | Instant File Initialization will only "instantly" initialize the .mdf (database data file). It will not instantly initialize the .ldf (log file). Perhaps your log file is fairly large, which would account for the restore taking longer, but not quite as long, as without instant file initialization. | |
| Oct 29, 2013 at 22:45 | comment | added | Sean Long |
I actually had tried that too, and I don't remember it being under an hour. I looked at the Technet article on restoring, but it doesn't look like ... WITH REPLACE does anything terrible, I think I just found a turbo button.
|
|
| Oct 29, 2013 at 22:44 | history | answered | Hannah Vernon♦ | CC BY-SA 3.0 |