It would be very helpful if restore operations through the gui used the default database data and log file directories defined for a sql server instance. this is an easy registry setting to find. When restoring a large database with many files, having to redirect the gui to the correct drive and directory for every file is really time consuming.
Comments
3 comments
-
Thanks for your forum topic. We already know this is a problem and have logged a bug as SB-3204.
SQL Backup does try to find the defaultdata and default log locations, but I think the problem is that SQL Backup is still using the registry paths that Microsoft used back in 2005. Please see this topic for a lively discussion on the subject:
http://www.red-gate.com/MessageBoard/vi ... php?t=9834 -
Any news on this bug SB-3204?
I'am using SQL backup V6.4.0.56.
Running SQL 2005 on a MSCS cluster.
Thanks
/Bosse -
SB-3204 says it's been fixed and should be released in SQL Backup 6.5. Of course this is severelyy subject to change in case testing reveals problems that get it taken out again. Also, our roadmap doesn't have SQL Backup 6.5 on it currently, so I can't say when it will be available.
Sorry I can't be more helpful.
Add comment
Please sign in to leave a comment.