Comments
1 comment
-
Hi,
Thanks for the feedback and for taking the time to give the beta a try.
You should be able to move servers between server groups by simply dragging ad dropping them.
The problem with grabbing all the CPU is a know issue, we will be putting in various performance enhancements for the final release that should improve this.
Unfortunately you cannot currently view the options for a 4.x server using the 5.0 GUI. This is because there are a number of options supported by the 5.0 GUI and server that aren't part of the 4.x server. It is something we will look at as to whether or not we can show the options for a 4.x server within the 5.0 GUI.
Well will have a look at the issue with importing SQL Server registrations ignoring server groups.
Thanks again for the feedback
Alan.
Add comment
Please sign in to leave a comment.
When importing SQL Server registrations from SQL Backup 4, the import process completely ignores the SQL Server groups that were created to organize the server registrations. In my case, I had four server groups defined: DEV, DR, QA, PRODUCTION. Groups alre also ignored when importing from Enterpise Manager or SQL Management Studio.
Additionally, I can find no way to move server registrations around among the groups once they are created. If I want to mover a server from the DEV group to the QA group, I am forced to delete and recreate.
Another issue that I see is that the "options" that I had configured for each server under the version 4 UI are not being read by the version 5 UI. Specifically, the version 5 UI is not retrieving things like default backup locations and file formats, email settings and such. Perhaps if this works fine for servers that have fully upgraded to version 5, but it is possible that users will be running a mixture of version 4 and 5 servers, so the new UI should probably work equally well with either version.
Finally, for whatever reason, the new SQL Backup 5 UI seems to grab my CPU and task it to 100% for an extended period of time after start up. I have about 20 servers registered, so perhaps it is busy pulling status data from each of the servers. Unfortunately this interferes with other things running on the machine and make some working in parallel with the app very difficult.