Comments
4 comments
-
Best guess is that it's busy retrieving and processing the backup history. Could you please run the following queries and let us know the results:
EXEC master..sqbdata 'SELECT COUNT(*) FROM backuphistory' SELECT COUNT(*) FROM msdb..backupset
Thanks. -
First query: 28153
Second query: 83665 -
It looks like the GUI and service are busy populating the local backup history data store. Is this the first time you are running the GUI to connect to this instance on this machine? If so, if you can let it run awhile, this would be a one time hit. Subsequent runs of the GUI won't need to store the backup/restore history details from scratch.
Thanks. -
Thanks. I'll let it run for a while and see how we go.
Add comment
Please sign in to leave a comment.
On a SQL Server with the following versions:
- Windows 2008 R2
- SQL 2005 SP3
- SQL Backup 6.4 (UI 6.4.56; SQBCoreService 6.4.0.1015)
When starting SQLBackup UI on the server it takes up to 100% connecting to SQL 2005 (green circle keeps running). When I killed the UI process, the SQBCoreService process was still using 45% CPU. I had to restart the service. There was no backup or restore running. All I did was just expanded the SQL Server in the SQLBackup UI.
Why are these two processes, particularly the UI, use so much CPU?