Reducing Database Growth Rates In Remote Desktop Commander

You are here:
  • Main
  • Agent
  • Reducing Database Growth Rates In Remote Desktop Commander
← All Topics

What options are there for reducing database growth rates?

1. Do not collect performance data with our agent altogether (by simply disabling the agent services on the session hosts).  This will only send data that allows you to see detailed CPU/Memory consumption by user.  You can utilize the dashboards to see performance by user, throughout each of their sessions, in a granular fashion.

The other reports (e.g. the Productivity Report, etc.) are populated by “session” data that is not dependent on the Agent Service for collection.  The Agent Data is what uses lots of space in the database, not the other reporting data.

2. Increase the time between Agent and Sesson data samples, which can cut database growth by 50% or more.  By default, the Remote Desktop Commander Service conducts a master poll of all data from monitored servers every 2 minutes, and its RDPSoft RDR Agent Service does a local collection of data each 30 seconds.  You can decrease the rate of polling (and subsequent database storage) by using one of the following 2 polling regimes:

Polling Configuration 1 (Lighter)

Master Polling Interval (Set this in the Polling Tab in the Remote Desktop Commander Configuration Tool):  180 seconds

Agent Collection Interval (Set in the registry on the session hosts after the agent service install):  60000 milliseconds

Set the HKLM\SOFTWARE\RDRAgent key, CaptureInterval value to 60000 on each session host with our agent service deployed.

Polling Configuration 2 (Lightest)

Master Polling Interval (Set in the Polling Tab in the Remote Desktop Commander Configuration Tool):  300 seconds

Agent Collection Interval (Set in the registry on the session hosts after the agent service install):  120000 milliseconds

Set the HKLM\SOFTWARE\RDRAgent key, CaptureInterval value to 120000  on each session host with our agent service deployed.

After making these changes, the agent service must be restarted on each session host, and the Master Polling Interval must be saved in the Remote Desktop Commander Configuration Tool, which will prompt a restart of the main Remote Desktop Reporter Service automatically.

3. Reduce the database retention.  Under the Remote Desktop Commander Configuration Tool, go to the Database tab, and change the Agent retention from 3 days down to 2 days or even 1.  You can leave the other session data at 60 days retention.