Forum / Devolutions Password Server - Support

Moving Backend SQL Database

  • Create an Issue
  • Cancel

We are going to be moving the SQL backend of our DVLS to another SQL cluster. Is there anything we should be cautious about or gotcha's that have come up from other people moving the database?

It appears its as simple as pointing to the new database server in the DVLS config.

Thoughts, comments?

Thanks,
Sam

Clock2 yrs

Sam,

Your best option is to create a backup using SQL Server Management Studio (SSMS) then restore it on the new SQL Server. You will need to "fix" your SQL logins using the "Fix SQL Login" (little hammer icon) in the DVLS Users screen.

Steps
- backup using SSMS
- restore using SSMS
- change DVLS configuration to reference new database location (DVLS Console > Edit > Database(tab))
- fix SQL Logins (DVLS Console > Users > select all users > Fix SQL Login)

All should be good at this point. To make sure your SQL schema is valid you can use the "Email Schema to Support" button (DVLS Console > Edit > Database(tab) > Email Schema to Support). Please add a simple message, something like "Please validate schema after database was moved to a different server". We will validate the schema to make sure everything is good and get back to you.

Like any database action. Make sure you have a good backup and that you keep that backup safe and secured until all has been validated and working. You might want to keep the actual database on the old server for some time after the move as a safety precaution.

Best regards,

Stefane Lavergne

signaturesignature

Clock2 yrs

I would also add. Stay away from third party moving/scripting tools. They usually script the "entire" database. Sometimes missing things like default constraints, indexes, triggers and/or views. They may also resets an internal database settings that may cause issues with the RDM/DVLS cache subsystem.

Best regards,

Stefane Lavergne

signaturesignature

Clock2 yrs

Great. Thank you Stefane for all your help.

Clock2 yrs