Timeline for SQL Server Migration restore backup vs copy data and log files
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 20, 2016 at 18:39 | comment | added | Kris Gruttemeyer | Are there any considerations to detach/attach since it is a version upgrade? Will that even work? I know with BACKUP/RESTORE the internal DB versions need to be upgraded when you restore to a higher version. I've never attempted a detach/attach, I always do backup/restore when moving up versions. | |
| Jan 21, 2012 at 12:35 | history | migrated | from stackoverflow.com (revisions) | ||
| Sep 16, 2009 at 14:24 | vote | accept | CommunityBot | ||
| Sep 16, 2009 at 14:24 | comment | added | Roger Lipscombe | It's possible that you don't want people accessing the database (for insert at least) once you've started the backup -- you'll be losing their changes when you restore it somewhere else. My point is this: sometimes downtime's unavoidable. | |
| Sep 16, 2009 at 14:19 | history | answered | gbn | CC BY-SA 2.5 |