Reducing Database Growth Rates In Remote Desktop Commander
What options are there for reducing database growth rates?
- First, enable the automatic weekly database re-indexing feature in the Remote Desktop Commander Configuration Tool. You can find this under the Database Tab – set it to a day like Sunday with lighter terminal server user activity, and it will automatically re-index your higher volume database tables which fragment quickly. This weekly re-indexing operation will free up large amounts of disk space in your database.
- Second, consider reducing the retention rates for session and agent data. The default rates, found under the Database Tab in the Remote Desktop Commander Configuration Tool, are 60 days for session data and 3 days for agent data. If you are using SQL Express, or are using a disk space constrained full version of SQL, please consider lowering these thresholds to 14 days of session data and 1 day of agent data, respectively. Then click “Save Changes.” At the next daily database maintenance time (the default is set to midnight), the software’s service will automatically purge records older than these thresholds from the database.
- Third, consider increasing the time between polling data samples, both by the primary Remote Desktop Reporter Service, and by any Remote Desktop Commander Agents running on remote session hosts. This can reduce database growth by 50% or even 75%. You can do this easily by running the Agent Tuning & Deployment Wizard, available under the Polling & Agents tab in the Remote Desktop Commander Configuration Tool.
Move the slider to the Light or Lighter setting to reduce polling frequencies, and then click “Adjust Advanced Agent Settings.” Check “Do Not Collect TCP/UDP Connection Data” which will also reduce database growth. Finally, click “Change Settings Only” and “Apply Changes” to push out this new configuration to existing servers that host our agent service. When the wizard finishes running, click “Close and Exit Wizard.” You can re-run this wizard with an even less frequent collection interval if you wish to further reduce database growth rates.
