Performance 2 - System Slowness
Your report of general system slowness has been logged with the technical team
When entering a ticket, we like as much information as possible about what part of the software you were in and what you were doing when you started to see the system slowdown. This information helps the technical team identify the possible causes.
If you haven't already, please provide:
1. The time when the issue started
2. What you were doing in ProviderSuite when you noticed the issue (running reports, entering payments, viewing schedules, etc.)
Sometimes slowness can be caused by Internet congestion at your location or at our data center.
If you experience continued system performance issues, please reopen the ticket to report any additional information.
Related Articles
ProviderSuite System Requirements
The most current system requirements can be found at http://www.practiceadmin.com/our-solutions/technology/ The minimum system requirements to run PracticeAdmin software: Reliable, consistent business quality Internet service — minimum Internet ...
Ticket Fields - Operating System
To help research issues related to accessing our software, including launching our Billing, Scheduling, and Receivables installed applets, we have a custom field on Product Support tickets in Zoho Desk. The "Operating System" field is a list of the ...
Speed Test
During an unexpected performance issue, please follow the steps below to rule out any possible ISP issues. Click on this link to access the Ookla Speed Test. Click "Go" to begin. Once completed, please take a snip/screenshot and attach it to the ...
System Note
Introduction This is quick reminder of how the notes function in PA. More Information Notes that are entered into the PA system can only be deleted the same day that the note is created and by the same person that entered the original note.
How to resolve ProviderSuite Database Performance Issues
General database performance issues 1. Identify and kill transactions that could be causing the problem - Result = transaction restarted, some users could be affected - Risk = kill a critical transaction that corrupts data 2. Stop/Start the SQL Job ...