Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Migration from 2012 to 2020
#1
Looking for some advice on this. 

We recently purchased through a new version of ASG Remote Desktop, and are looking to get going with the migration. As I understand, simply installing the new version on my Desktop and Linking to the appropriate database will allow me to function with the legacy database. I can then go through the option to update the Database to the new version.

When I go through this database update, will those of my staff still using the older version still be able to connect to the database or will the changes to the database render them unable to connect?

As part of this update I would also like to move the database to a new SQL server that we have provisioned. What is the best way to move between SQL servers? Is the Export and Import function that I notice likely the best method or would using native SQL tools provide better results?

Thanks in advance.
Reply
#2
Migration from 2012 to any version above is 2015 is different as normal updates - as the scheme changed with version 2015 you can only create a new database with version 2020 and then "Upgrade your old data to the new database - choose Environment=>Upgrade from 2012" - the data will be read, transformed and then recreated in the new database - the old database will not be changed! So perhaps a good step for using the new SQL server :-) You can test version 2020 and then migrate your users...

If you have huge logs (>10k rows) you should delete them before the migration - otherwise it could fail...

If you run into any issue - just ask again!
Regards/Gruss
Oliver
Reply




Users browsing this thread: 1 Guest(s)