Timeline for Migrate all databases from one SQL Server 2005 to another
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 12, 2023 at 11:21 | history | edited | Glorfindel | CC BY-SA 4.0 |
5 broken links fixed, cf. https://meta.stackoverflow.com/a/406565/4751173
|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Sep 24, 2014 at 7:14 | vote | accept | Armin | ||
| Sep 24, 2014 at 7:14 | comment | added | Armin | Thank you sir. This is a really definitive answer and has described all aspects of the issue perfectly. In fact we can have downtime for about 2-3 hours and this is enough for backup and restore. This answer is great. Thank you guys | |
| Sep 24, 2014 at 1:16 | history | edited | Kin Shah | CC BY-SA 3.0 |
added 285 characters in body
|
| Sep 23, 2014 at 16:22 | comment | added | James Anderson | I too use the log shipping method to reduce down time. I generally manually configure the system DBs and use scripts I have to sych logins and bring DBs online. Gives more time on the day to sort any issues. | |
| Sep 23, 2014 at 15:44 | history | edited | Kin Shah | CC BY-SA 3.0 |
added 187 characters in body
|
| Sep 23, 2014 at 15:43 | comment | added | Kin Shah | Agreed with that .. will update my answer. | |
| Sep 23, 2014 at 15:36 | comment | added | Shanky | But still I think if you add about backup and restore of user with system database and remove about logins and jobs migration you would make your answer more complete. Like you said it lies with OP to decide. | |
| Sep 23, 2014 at 15:33 | comment | added | Kin Shah | there are many steps that can be done pre migration. What I normally prefer is to have as minimum downtime as possible during the actual day of migration, so that there is ample time for testing and addressing any issues that might come up. The steps mentioned are the ones that I have actually implemented. | |
| Sep 23, 2014 at 15:30 | comment | added | Shanky | I was thinking more in terms of will it be eaiser to backup and restore of 200 database with system databases or creating logshipping or mirroring for 200 databases and then manually moving all jobs and logins and other packages if required. | |
| Sep 23, 2014 at 15:27 | comment | added | Kin Shah |
@Shanky if you read my answer, I have mentioned that restore the tail log backups on the secondary with recovery bringing all the secondary databases online. Also, the different links are for optimization that are very relevant for sql server 2005 and up. That makes the answer more relevant. I would rather leave with the OP to decide which answer will help. At the end, we all are here to help and get help.
|
|
| Sep 23, 2014 at 15:11 | comment | added | Shanky | OP never said he is not ok with little downtime as a fact with mirroring and logshipping during 'cut over' there would be downtime and your answer does not include basic thing about restoring system database backup. I dont know why you put different links | |
| Sep 23, 2014 at 14:38 | history | answered | Kin Shah | CC BY-SA 3.0 |