Upgrading from 2022.1.27 to current version

Hello,

Thank you for reaching out to us regarding this.

From my knowledge, you should not encounter any issues; however, we always recommend performing a backup before an upgrade, so that it can be easily restored in case such an issue occurs.

You can follow this knowledge base article for the upgrade process:
https://docs.devolutions.net/rdm/windows/installation/database-upgrade/

Let me know if this helps, or if you have further questions.

Best regards,

Hi generbillings



Problem we had that the RDM upgrade to version> 2023.2.x upgrades the database, and transforms subconnections to sub-entries. OLD RDM instance connecting to an upgraded DB will suddenly see all original subconnections as separate entries, as if they 'fell off' their parent.

https://blog.devolutions.net/2023/01/goodbye-sub-connections-hello-much-better-sub-entries-in-rdm/
it says:

Starting in RDM 2022.3, we have replaced sub connections with sub entries. Discover why we made this change, and why it’s a significant improvement. .....
(specifically: v2022.3.4.0)

This gave us so much problems (multiple times) that we decided to postpone the upgrade until we migrated to new SQL server.
We then backup/restored the RDM database to a new server, upgraded RDM on a few machines, connecting to the NEW instance.
during migration, the non-migrated RDM instances are connected to old SQL database, upgraded ones to new SQL Server.
We use version management in the datasource to make sure only older RDM instances could connect to old SQL, and newer RDM to new.

a.f.a.we know, if you're not using subconnections, there is no problem.
But DO NOT try to connect with a <2022.3.4 version of RDM to a migrated datasource, it will show as if all subconnections have become 'unparented'

Regards, Ben

Hi generbillings



Problem we had that the RDM upgrade to version> 2023.2.x upgrades the database, and transforms subconnections to sub-entries. OLD RDM instance connecting to an upgraded DB will suddenly see all original subconnections as separate entries, as if they 'fell off' their parent.

https://blog.devolutions.net/2023/01/goodbye-sub-connections-hello-much-better-sub-entries-in-rdm/
it says:
Starting in RDM 2022.3, we have replaced sub connections with sub entries. Discover why we made this change, and why it’s a significant improvement. .....
(specifically: v2022.3.4.0)


This gave us so much problems (multiple times) that we decided to postpone the upgrade until we migrated to new SQL server.
We then backup/restored the RDM database to a new server, upgraded RDM on a few machines, connecting to the NEW instance.
during migration, the non-migrated RDM instances are connected to old SQL database, upgraded ones to new SQL Server.
We use version management in the datasource to make sure only older RDM instances could connect to old SQL, and newer RDM to new.

a.f.a.we know, if you're not using subconnections, there is no problem.
But DO NOT try to connect with a <2022.3.4 version of RDM to a migrated datasource, it will show as if all subconnections have become 'unparented'

Regards, Ben

Hello Ben,

Can you confirm if you get the same problem with version 2023.3.34.0 of RDM ?

Best regards,