I'm a developer on the SQL Backup UI; thanks for leaving feedback.
We're aware that a number of users of the UI have seen performance issues in areas particularly relating to activity history; we've done some investigation work, but unfortunately, these issues are proving hard to replicate in an artificial test environment, and my suspicion is that many of them are down to a combination of the UI's update mechanism, quantity of data and the environment in which both the UI and server is running. The work is ongoing, however, and it would really help if you could answer a couple of questions - feel free to send me a private message or email me at email@example.com
if you'd rather not answer these publicly.
1) Could you describe your setup? (SQL Server version, CPU, memory, disc space, number of DBs, backup frequency, etc). In particular, how my entries in the activity history (approximately) would you say there are, and how many new entries per day are added?
2) How often would you typically launch the UI? And does the problem occur every single time you launch the UI, or only if it hasn't been run for a while?
2a) In particular, after you left the UI running over dinner, did the same problem recur the next time you opened the UI, or was it more responsive on subsequent occasions?
3) Do you run the UI on the same machine as the SQL Server instance, or on a different machine?
4) If they're running on the same machine, is the user profile (in particular, the AppData directory) of the user running the UI stored on the same storage device as the SQL Server database files or SQL Server instance?
5) Is/are your SQL Server(s) particularly heavily loaded, either in terms of CPU or IO? (or would they typically be so when running the UI?)
Thanks very much;