If I take a backup that was made on one of our production servers running SQL Backup 5.3, and attempt to restore it on a development server running the pre-release verison of 6.0, the restore wizard does not behave in what I would call a logical way.
In step 2 of 4, I have to choose either overwrite existing database, or create new database. If I choose to create a new database, I would expect the wizard to default the database name to that of the database that was backed up, but instead I have to type in the name. This is consistent with the behavior of 5.3, but could be improved.
Seemingly different from 5.3, however, is that once I type in the name of the database, even though SQL Backup uses the name to adjust the filenames of the mdf and ldf files to be created, if I need to place those files on a different disk than the default, as soon as I click the ellipsis to pull up the file browser it looks in the default file location and replaces the file name it had previously "calculated" with the first file listed in the default folder.
This is especially perplexing when the first file in the default folder in an mdf file and the filename being specified is for a transaction log. If there is a reason for this curious behavior, I'd like to know what it is, since the lack of a scheduled restore function in this release means I am likely to continue having to do a number of manual restores, and would prefer not to have to do all the extra typing.
In step 2 of 4, I have to choose either overwrite existing database, or create new database. If I choose to create a new database, I would expect the wizard to default the database name to that of the database that was backed up, but instead I have to type in the name. This is consistent with the behavior of 5.3, but could be improved.
Seemingly different from 5.3, however, is that once I type in the name of the database, even though SQL Backup uses the name to adjust the filenames of the mdf and ldf files to be created, if I need to place those files on a different disk than the default, as soon as I click the ellipsis to pull up the file browser it looks in the default file location and replaces the file name it had previously "calculated" with the first file listed in the default folder.
This is especially perplexing when the first file in the default folder in an mdf file and the filename being specified is for a transaction log. If there is a reason for this curious behavior, I'd like to know what it is, since the lack of a scheduled restore function in this release means I am likely to continue having to do a number of manual restores, and would prefer not to have to do all the extra typing.