Unable to connect to the database after system swap
I changed my system and the new laptop doesn't let me load my database.
It was still working on my old laptop with exact same configuration.
I have uninstalled it now from the old system to make sure only one license against my id is utilized however it's still giving the same error message.
Attached the error details.
RDM Issue.docx
All Comments (9)
Hello,
Thank you for contacting the Devolutions Support Desk !
What RDM version are you using ?
Also, are you able to login to the SQL server using the same login information and authentication method in SSMS ?
Best Regards,
We are using 12.6.8.0 for a reason, now I learned all in my team facing this issue with this database.
Hello,
Could you email us your database schema from RDM ?
You'll need to select this option here: 
Best Regards,
I have emailed the schema details through my account.
Please let us know once we have a solution, as our db team is waiting for your instructions on what to do next.
Hello,
We've received your database schema, thank you for sending them.
I've given your database schema to one of our engineers for review, and I will get back to you with news once I receive word from them.
Best Regards,
thanks for your quick response, as we had to try few options while waiting for your response, we restored the backup of db from last back and it was not showing available servers in the list, however for some reason it worked. looks like the schema was changed or updated for some reason causing this issue. Please let us know if it was an issue with something else apart from 2 additional tables added on either 9th or 10th of March.
Hello,
I'm glad you could get things working again, while I'm not aware of what the source of the issue could be, I would highly recommend that if you wish to stay on this version you make sure no one is updating RDM as doing so will require database upgrades on your data source.
Database upgrades restructure the database RDM uses in order to allow compatibility with the latest versions and it's features.
Our engineer still has the database schema and will possibly be able to give you a more concrete answer on what may have happened if you wish to know more, however from what I was told the error you were receiving was fixed in version 14 of RDM.
Best Regards,
Hello,
Just to add to my last message, you can actually configure which versions of RDM are permitted within the database to prevent users from updating RDM and then forcing a database upgrade.
The option, titled "Version Management" should be under Administration > Data Source Settings:
Best Regards,