19-05-2020, 10:29 AM
Hi Centura,
The 2016 database could be used in 2020 but needs migration. To be able to do that its a good idea to import the new license (you need for the 2020 version) into the 2016 environment. Because otherwise the old license in the database might prevent a migration. Then a migration dialogue should be displayed asking for a useraccount that has needed database access for that. Should be done in seconds. That's it.
It's advisable to do a backup first or create a clone first if you want to have a safe copy of you old environment.
Hope that helps,
best regards,
Michael
The 2016 database could be used in 2020 but needs migration. To be able to do that its a good idea to import the new license (you need for the 2020 version) into the 2016 environment. Because otherwise the old license in the database might prevent a migration. Then a migration dialogue should be displayed asking for a useraccount that has needed database access for that. Should be done in seconds. That's it.
It's advisable to do a backup first or create a clone first if you want to have a safe copy of you old environment.
Hope that helps,
best regards,
Michael
best regards,
Michael -- michael.scholz@asg.com --
Michael -- michael.scholz@asg.com --