10-10-22 02:48 PM
Hello guys,
We are in the process of updating Blue Prism from version 6.5 to 6.10.5.
But when I updated the Database a new version was created.
Both in the documentation and in the tests I was not able to use the DB from version 6.10.5 to 6.5 to proceed with the migration, as we will be doing it in phases from October/2022 to December/2022.
I would like to know if I can use only one DB to perform this migration or will I really have to keep both DBs active until completion?
Awaiting.
Thanks.
Answered! Go to Answer.
20-10-22 03:20 PM
Hello,
what Paul suggested is technically correct, but would say it might be an "overkill" .
If your scope is not too big (let's say you plan to do the transition in two or three weeks) than there is probably no need for you to keep two parallel DEV environments.
Yes, it's true you won't be able to deploy, but you don't risk the forks (plus there is always a possibility to do an emergency change straight in PROD).
Another thing I would mention is, that there is no need to create an empty 6.10.5 environment, you can just do a backup of the old DEV environment and then go straight for the upgrade. Or (if you want to run two DEV environments) make a clone and upgrade a clone. That way there is no need to transfer the objects, processes, credentials, calendars or to recreate the changes you have made to your db (i.e. local holiday added).
We are going through 6.10.1 -> 7.1.1 right now, have it planned for two weeks (we have 4 licenses and almost no usage of the problematic invokes).
11-10-22 07:36 AM
20-10-22 03:20 PM
Hello,
what Paul suggested is technically correct, but would say it might be an "overkill" .
If your scope is not too big (let's say you plan to do the transition in two or three weeks) than there is probably no need for you to keep two parallel DEV environments.
Yes, it's true you won't be able to deploy, but you don't risk the forks (plus there is always a possibility to do an emergency change straight in PROD).
Another thing I would mention is, that there is no need to create an empty 6.10.5 environment, you can just do a backup of the old DEV environment and then go straight for the upgrade. Or (if you want to run two DEV environments) make a clone and upgrade a clone. That way there is no need to transfer the objects, processes, credentials, calendars or to recreate the changes you have made to your db (i.e. local holiday added).
We are going through 6.10.1 -> 7.1.1 right now, have it planned for two weeks (we have 4 licenses and almost no usage of the problematic invokes).
20-10-22 07:49 PM
21-10-22 12:15 PM