MS SQL Express vs. Enterprise vs. Standard

There will be very little noticeable performance gains running RDM on Enterprise vs Standard vs Express.

RDM does simple CRUD (Create, Read, Update, and Delete) for the most part.

If we talk about RDM data size we are talking what, 20,000 entries split over 10-20 vaults for a very big installation. Those are rookie numbers for any SQL engine (MS SQL or other).

The only thing you might have to keep in mind is the clear/clean your RDM logs (activity logs, entry history, deleted history) and make sure you have proper SQL backups and database transaction log file management and you're good to go.

Hello Stéfane

Thank you for the information.

With kind regards,
Nick

Nick,

One more thing that I forgot to mention in my last post. The number of users accessing RDM needs to be considered. For example, 10 vs 2000+ users will make a significant difference on the workload on the server.

Best regards,

Hello Stéfane

Thank you for the information.

We have one vault that is slow (no virtual folders or other items that we are aware of that could slow it down).
It has approximation 8K entries and around 100 users. Some users can access the vault within 15 seconds, others have to wait a minute or longer.

The slow-down is especially noticeable when adding or editing entries.

With kind regards,
Nick

Nick,

There are a few steps you can take to look at where or what is causing the slowdown.

First would be to get a base line idea of performance.

1. On machine that is at 10-15 seconds
2. Help > Profiler
   1. Set the "Profiler level" = 1 & make sure "Auto clear" is checked
3. CTRL + refresh that data
   1. this will give you a high-level trace of the time spent loading the data
   2. RefreshConnections : 0000 ms will give you the overall and going up will give you a breakdown.
4. Now do this a slower machine and compare the results

Now you have an idea. We can narrow it down. Could it be the SQL Server?

1. Set the "Profiler level" = 3
2. CTRL + Refresh
3. The output will also about the SQL statements and the total execution time.
   1. Look for large 0000 ms values within the profiler window

As for edits

1. Clear the profiler window (clear button bottom right)
2. Uncheck "Auto clear"
3. Edit an entry
4. Click "OK"
5. Back to the profiler
   1. Look for large 0000 ms values within the profiler window

PS: You can post your profiler results for me have a look at if you want further analysis.

Best regards,

Hello Stéfane

Thank you for the feedback. I'll try to test this tomorrow and will keep you posted.

With kind regards,
Nick

Hello Stéfane

Thank you for the tips, we found the issue by using the profiler. It seems that our network is the issue.

We will try to fix the network first. If the issue persist, I'll let you know.

With kind regards,
Nick

Nick,

Good news, keep me posted and let me know if you need further assistance.

Best regards,

Hello Stéfane,

We will. I forgot to mention that CPU also seems to make a difference. Users with a lower spec CPU need to be more patient...

With kind regards,
Nick