Timeline for Why does restore take a long time?
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 18, 2012 at 19:22 | comment | added | Jason Cumberland | w00t, glad it helped! | |
Jan 17, 2012 at 20:57 | comment | added | O.O | @JasonCumberland - I did what you suggested and both backing up and restoring combined takes less than 1 minute. | |
Jan 17, 2012 at 18:33 | vote | accept | O.O | ||
Jan 17, 2012 at 18:24 | comment | added | Jason Cumberland | You could switch to SIMPLE mode and the log wouldn't keep any bigger but in order to reduce the restore time you would still need to shrink the log file down to a more reasonable size. simple-talk.com/sql/database-administration/… | |
Jan 17, 2012 at 18:22 | comment | added | gbn | @subt13 you need an LDF regardless. Choice of recovery model is unrelated (except for whether you need log backups or not). | |
Jan 17, 2012 at 17:40 | comment | added | O.O | Yes, that looks to reduce the time it would take to restore. One more thing, we don't care about the LDF file, does that mean we should also switch to simple recovery model? | |
Jan 17, 2012 at 17:35 | comment | added | gbn | @subt13: the file on disk must be written with zeroes. See the link I posted on IFI please: "Data and log files are first initialized by filling the files with zeros..." | |
Jan 17, 2012 at 17:23 | comment | added | O.O | Can you explain what you mean by the LDF must be zeroed? Will this make the LDF smaller than 67 gigs? | |
Jan 17, 2012 at 17:21 | comment | added | O.O | Oh, good point. I just noticed the MDF file is ~2 gigs, but the LDF file is 67 gigs | |
Jan 17, 2012 at 17:12 | history | answered | gbn | CC BY-SA 3.0 |