September 17, 2018 at 10:29 pm
I have a SQL Server 2016 Standalone server with one of client application, I want to migrate current SQL 2016 standalone server to SQL 2016 AlwaysOn Availability Group cluster. Following the my concerns,
a. Application connection string configured to SQL standalone server FQDN since I want to migrate with the same name (FQDN). Base on application limitation I unable to change application connection string.
b. And I want to do this within minimum down time
hence I want to know which is the best possible way to do this migration without changing FQDN & within minimum down time, I really appreciate if someone can help on this.
Thanks
Harshana
September 18, 2018 at 3:07 am
You can always build 2 new servers, call them what you want, turn on clustering, install sql, turn on always on, copy your database, then add a listener with the name of your current server (will need to switch old server off at this point, but then if you want up to the minute, you will need to switch it off before you backup and restore your database). Downtime will be anywhere from a few minutes to a couple of hours depending on your database size etc (if you also take a log backup, you can restore to the secondary with no restore and then simply join).
Can't think of another way if you can't change the connection strings on your application.
September 18, 2018 at 3:17 am
Hi Rick
Thanks a lot for your reply.
Me too though same way but I bit confused that's why I put in to blog, I confident to do that now, thanks a lot for your help.
Harshana
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply