This category affects all data source refreshes, therefore
1.Initial load at program startup.
2.Prior to an Edit operation: by default, we reload the entry to ensure that we are working on the current version)
3.Prior to establishing a connection: we need to insert in the activity in our Usage Log.
4.Whenever you use Refresh: Depending on your cache settings, we typically just get the changes that occurred since your last refresh
5.Whenever you use
SQL Server has certain particularities that, if the default configuration are used, will cause performance degradation as time goes by. Please consult SQL Server Performance.
Custom images need to be stored in the data source, this results in the size of the configuration becoming problematic if there are too many entries using them. If that becomes the case it would be better to revert to built-in images.
Heavy usage of RTF description
RTF in itself is not a real issue until you decide to embed images in the description. This results in the same problem as using custom images, namely the size of the configuration becoming too large. If that becomes the case, reduce the size of your descriptions.
When you enable the Offline Mode, a local file is created and is kept in sync with the data source. This file is encrypted using the Windows built-in NTFS encryption which can cause delays in refreshing the local data file. This is rarely the case but seems to happen on computers on a domain which has been hardened by the network administrator. You can turn off this option by unchecking Use NTFS Encryption for offline mode in File - Options - Advanced.
The new Ribbon UI is modern and allows for infinite variations of panel organization, but it does take more calculations by the UI layer. On most system this is not a cause for noticeable performance slowdown, but on others setting the User Interface to Classic UI (v7.x) in the general options tab will definitely help.