Database Limit
We are using Microsoft SQL Server 2008 for our database. The database is almost a year old. There are 3,110 entries and the size of the database is 412MB and the log is 833MB. Is there a limit to the number of entries or size of the database that would start to cause connection errors or timeout issues?
edited by David.Odendahl on 4/24/2013
RDM error.jpg
All Comments (1)
David,
First of all, make sure you have a good backup and disaster recovery plan in place. You don't want to find out one day that you've lost your entire database of 3000+ sessions and you had no backup. A proper backup plan, including log backups, will also make sure your log file size is under control.
http://help.remotedesktopmanager.com/index.html?bestpractices_backups.htm
With over 3000 entries in RDM you probably see some performance degradation when performing edits, adds, deletes and refreshes. To alleviate that we are currently working on an Intelligent Caching mechanism that will greatly improve performance on that level.
As for timeout and connection errors there should be no real side effects. SQL Server is capable of much more then that.
There are however memory issues with some connection types. RDP to Windows 8 or Server 2012 for instance may cause high memory usages as documented here:
http://forum.devolutions.net/topic2647-too-many-tabs--protocol-error.aspx
possible solution here:
http://help.remotedesktopmanager.com/index.html?troubleshooting_largememoryawa.htm
Stéfane Lavergne