Comments
3 comments
-
Hi,
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
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\DefaultData
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\DefaultLog
If entry does not exist or empty :
HKLM\Software\Microsoft\MSSQLServer\Setup\SQLDataRoot
This area of SQL Backup is being looked at for the next release and should be improved.
Thanks -
I set the DefaultData and DefaultLog values in the registry as "E:" and "F:" respectively. SQL Backup 5.3.0.178 uses the DefaultData directory but appears to ignore the DefaultLog directory when restoring to a new database.
-
Hi,
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.
Thanks,
Add comment
Please sign in to leave a comment.
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.