Why use Server if we already use RDM?
I work with a small team, and we use RDM and love it. Why would we want to use Devolutions Server? What does it give us that RDM doesn't? If we wanted to use Server, does it use the current database that RDM uses?
All Comments (2)
Hi,
For small teams, I wont highlight the ease of management and seamless integration with AD/AAD, its probably not a big selling point for you.
its mostly about security:
- Encryption in transit (you could do that already with encrypted connections... depends on your SQL instance)
- Encryption at rest : sensitive data is encrypted with a key specific to your installation
- Database isolation : your users go through our middleware (the server) and the DB is never accessed directly
A few notables :
- Server side synchronizers (AD and VMWare) - runs on a schedule without RDM being involved
- SMTP integration : Alerts and notifications can be sent via email
- Reports (do you need compliance?)
Because of the "Encryption at rest" feature, your database will be altered and become unusable for direct connection by RDM
Again for other readers, we obviously have a LONG list of reasons why DVLS is better than a direct DB connection, but I'm adapting for a really small team that (I presume) does not need compliance...
I hope that's sufficient info. With our new DVLS Free tier, you could clone your DB and give it a try (please keep a backup of the original in a safe place)
Best Regards,
Maurice
Cloning the database and trying it out is an excellent suggestion. I'll see if I can do that. Thank you for the reply!