Below are some steps to check to troubleshoot the performance:
A. Set the DBTRACE at client level following the steps below:
1. Run the initeditor.exe and check the flag dbtrace or edit the C:\ProgramData\Quest Software\Stat\6.x.x\stat.ini file setting the parameter dbtrace=y.
2. Log in the Stat client again if you were logged in and in the coming popup set the directory where the dbtrace.log will be written.
B. Use tracert utility from Citrix against the Stat DB server and the SCA machine to see how long it takes to reach the target over the network.
For example: C:\ tracert <DB_server_name> and <SCA_server_name>
C. Make sure that the Stat windows clients can read the information from the registry.
D. Check if the Stat tablespace have enough space and in case increase them.
E. How far is the SCA from the stat db, psoft dbs, ebiz dbs and etc? To have better performance, we would suggest the SCA to be closer to the stat db, psoft dbs and ebiz dbs.
F. Try by running the following Stat maintenance jobs:
Purge Audit Tables
Purge Deleted Archive Sets
Purge Error Log Tables
Purge Migration Event Tables
*For a brief functionality description for these jobs, refer to Stat 6.3.0 System Administration Guide, page 165, topic "Defining Agent Jobs".
G. Consider also purging old CSRs might help. In this case, follow next kb article: https://support.quest.com/stat/kb/124060/purge-old-csr