What are the challenges you face when working across database platforms? Take the survey

Enhancement Request: SQL Backup

edited September 12, 2008 3:41AM in SQL Backup Previous Versions
I'm in the process of migrating from one SQL Server to another and using SQL Backup on the new server to perform the restores from SQL Backup backups on the old server. The one thing that's really driving me nuts is that I have to set the Data and Log file directories for EVERY restore. I have found that this is necessary even when restoring files to their original locations on an individual server.

It would be nice to be able to specify the default data and log file directories in SQL Backup via the Options panel or at least have SQL Backup use the SQL Server Defaults.


  • Options

    Thank you for your post into the forum.

    SQL Backup checks the following registry entries to determine the default Data and Log file locations used by SQL Server :

    SQL 2005

    HKLM\Software\Microsoft\Microsoft SQL Server\<instance name>\Setup\DefaultData

    HKLM\Software\Microsoft\Microsoft SQL Server\<instance name>\Setup\DefaultLog

    If entry does not exist or empty ::

    HKLM\Software\Microsoft\Microsoft SQL Server\<instance name>\Setup\SQLDataRoot

    SQL 2000



    If entry does not exist or empty :


    This area of SQL Backup is being looked at for the next release and should be improved.

    Matthew Flatt
    Redgate Foundry
  • Options
    I set the DefaultData and DefaultLog values in the registry as "E:" and "F:" respectively. SQL Backup uses the DefaultData directory but appears to ignore the DefaultLog directory when restoring to a new database.
  • Options

    You are quite right, this seems like a bug in the GUI.

    I apologise for the inconvenience, this will be looked at for the next release.

    Matthew Flatt
    Redgate Foundry
Sign In or Register to comment.