Post reply

SQL Server Migration

  • October 11, 2015 at 7:48 am

    #304164

    Comments posted to this topic are about the item SQL Server Migration

  • October 12, 2015 at 5:27 am

    #1832781

    Any reason you didn't simply use P2V?

  • October 12, 2015 at 4:12 pm

    #1832891

    Alex Friedman (10/12/2015)

    Any reason you didn't simply use P2V?

    Of course P2V is less complex in terms of migrating SQL but I think the point here was to make a guide that could be applied to any SQL Server instance migration, no? 🙂

  • October 13, 2015 at 6:51 am

    #1832979

    Hi Alex, what I didn't mention in the article was, we upgraded the OS in these migrations. Another requirement was we had to change the drive letters of the new system to meet standards. I've personally never done a P2V before, but I hear great things about them!

  • October 21, 2015 at 7:36 am

    #1834660

    Thanks for the detailed article.

  • October 26, 2015 at 2:37 pm

    #1835599

    you're welcome!

  • October 26, 2015 at 3:06 pm

    #1835605

    Wonderful .. it really helpful to me

    Thanks

  • October 29, 2015 at 7:42 am

    #1836371

    amzadali16, thanks! glad it was useful to you. : )

  • November 24, 2015 at 10:17 am

    #1842122

    Great success in Using this!!! Thanks a Million Geoff

  • July 20, 2018 at 2:19 am

    #1998342

    Hi GeoffRuble-976616,

    Is there any reason why going into sql server configuration mmc and changing the master database path there pointing to the new master database not work? which is essentially overwriting or swapping out the new master db with the one you already have? forgive me if am being a bit ignorant as my sql knowledge is at novice level.

    Regards,
    Waqar

  • July 20, 2018 at 2:10 pm

    #1998475

    Great detail on your methodology.

    I would suggest taking a look at the powershell module dbatools.io.  It will take care of a lot a lot of your steps for you and others that might have slipped your mind.

  • September 12, 2018 at 12:09 pm

    #2005479

    Hi All,
     I never comment on this kind of subject, but this one is very important. I been part of a lot of migration and do it this way have a high risk and even Microsoft don't recommend this if you didn't test all your application. If you have only 1 application, this could be done, but in most of the company their have shared SQL with more than 1 application. The rollback will be for all your applications and not just one if only one failed. I'm not telling you is not good of the point of view technical but in the point of view business, this is too much risk.

    Manuel

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply