Question about Limitations RDM client
Good day!
We are looking into the option for using RDM as our default tool for managing connections.
Is there a current limit of Entries or connections within the client?
Does anyone have a example or article which can build on this further?
Please let me know if you have any questions!
All Comments (3)
Hi,
RDM shows a warning when you reach a certain number of entries, but it’s dependent on your chosen data source. It ranges from 3000-5000 I believe.
Serialization, Decryption, applying RBAC, etc. is costly and we need to find a balance between supporting large datasets and usability.
RDM allows you to store so much information on entries, even going as far a allowing binary documents to be attached. Users that make use of this will need to keep lower counts than our recommended tresholds.
What numbers did you have in mind?
Maurice
Hello Maurice,
Thank you for the quick Response,
We do not have an accurate estimate, but it is possible to have more than 5000 entries when working with the software.
This will not only be RDP connections but also things like Credentials, documentation and Folders for infrastructure.
The current plan is to use a SQlite database as our storage location.
Could you give me advice in how we can resolve this when there are more entries?
We are also interested in the differences and options between the possible data sources we can use in RDM.
Feel free to ask me for more information when needed!
Hello,
I must've been half asleep, I wrote the prologue and didn't finish my idea.
When using a team datasource, the first level of containerization of data is called a VAULT. You can have a large number of vaults, enterprises create vaults per teams/departments, whereas MSPs create vaults per customer. So the limits in my previous answer were per VAULT.
Sadly, Mysql is not a TEAM datasource, its meant for individuals and is stored locally. Team datasources are SQL Server/Azure, Password Hub Business (our SAAS offering), Devolutions Server (Self-Hosted).
SQL Express (which is free) is perfectly fine for the majority of our users. When using SQL, most of our customers put in place DB accounts for each user and set the permissions manually.
For a good overview of Hub vs Server, please consult this use case
Devolutions Server or Devolutions Hub Business?
Maurice