Marc Beausejour
Microsoft SQL Server (MSSQL) has been a common choice for a shared Devolutions Remote Desktop Manager (RDM) data source for a long time. It’s familiar, performs well, and is easy to deploy.
The issue today isn’t MSSQL Server itself. It’s the architecture most teams end up with: user machines with direct network access to the database that stores sensitive operational data. This increases exposure, creates more points of failure, and adds ongoing administrative overhead.
Devolutions Server vs. Hub Business: a quick decision checklist
The best option is to move away from direct MSSQL shared data sources and switch to a self-hosted or cloud-hosted data source. Instead of every RDM client connecting to the database, users connect to a service layer that centralizes access and reduces the number of places where permissions, connectivity, or configuration can go wrong.
That’s the shift behind Devolutions Server and Devolutions Hub Business. Devolutions Server gives you a self-hosted data source, while Hub Business gives you a cloud-hosted one. Both replace the direct-to-database RDM access with a DVLS or Hub-backed secure access model.
Pick Devolutions Server if most of these are true:
- You need self-hosting for compliance, customer requirements, or internal policy.
- You want full control over infrastructure, upgrades, and where data lives.
- You’re comfortable operating a server application within your environment.
Pick Devolutions Hub Business if most of these are true:
- You want to reduce infrastructure ownership and ongoing maintenance.
- You want a faster rollout with fewer dependencies on database hosting and connectivity.
- You prefer a cloud-first approach for shared vault access and collaboration.
If you’re split, use this tie-breaker: if maintaining servers is part of what you want to reduce, Hub Business is usually the better fit.
Migration made easier
The smoothest way to move off direct-access MSSQL is usually a phased rollout: set up the new data source, migrate the data, validate it with a small group, then move the rest of the team to the new shared data source in RDM.
Moving from direct-access MSSQL to Devolutions Server
If you want a self-hosted destination, use the migration wizard in the Devolutions Server console to move from MSSQL Server, including Azure SQL, to Devolutions Server.
Follow the step-by-step guide here: Migrate vaults from MSSQL Server to Devolutions Server
Our suggested transition path looks like this:
- Deploy Devolutions Server alongside your current data source.
- Back up the database.
- Run the migration wizard and validate the migrated data with a small group of users.
- Roll out to the broader team.
- Once everyone is switched, lock down direct SQL access and retire the old shared data source.
Moving from direct-access MSSQL to Devolutions Hub Business
If you want a cloud-hosted destination, move your vaults from MSSQL into Hub Business by exporting them from the data source and importing them into Hub Business.
Follow the step-by-step guide here: Migrate vaults from MSSQL Server to Devolutions Hub Business
A practical rollout looks like this:
- Create your Hub Business and add it as a data source in RDM.
- Back up the existing database.
- Export vaults from the data source and import them into Hub Business.
- Recreate and verify permissions during the migration.
- Validate with a group of users, roll it out more broadly, then retire the MSSQL data source.
Why this improves both control and day-to-day work
Whether you’re focused on reducing risk, keeping systems reliable, or simply saving time, the benefits are the same.
Security and control
- Fewer endpoints can attempt to reach the sensitive backend.
- Access is enforced through a service layer rather than direct database access.
- You reduce side-door access patterns created by direct MSSQL connectivity.
Operational efficiency
- Less time spent troubleshooting workstation-by-workstation MSSQL connectivity issues.
- Cleaner onboarding and offboarding because access is managed through the platform.
- Fewer special cases in network and permission management.
More than a replacement for MSSQL sharing
Moving to Devolutions Server or Devolutions Hub Business is not just about reducing exposure and simplifying administration. It also gives you access to platform features that are not part of a direct MSSQL setup, including access approvals, Single Sign-On (SSO), secure messages, and privileged access workflows. For teams that choose Devolutions Server, that can also include server-side synchronization, email notifications, GeoIP restrictions, Syslog integration, and Azure Log Analytics support.
If you need help with migrating over to a new data source, our support staff is ready to assist!
Steven Lafortune
France Lymburner
