I have a customer who is trying to restore their own customer's databases, and have the restored mdf and ldf files go to the respective default data and log file locations for that SQL instance; eg c:\sql. What they are finding is that this works for
most database restores, and the mdf files and ldf files will be automatically created in the c:\sql directory; however certain databases will try and recreate under the SQL install default directory of eg: c:\program files\Microsoft SQL Server\MSSQL.1\MSSQL\data.
This is a problem as they want the restore to be easy for their support guys to manage, and they are finding that sometimes databases are created in the wrong location
The only common themes here are that this is occurring on SQL Server 2005, and not 2008; and that it is the same databases everytime. They are also using the SQL Server Enterprise Manager GUI to do the restores, rather than command line.
Although I haven't ever studied this in great detail before, what I have always found is that a database which was maybe hosted on d:\SQLdata on one server will try and restore to d:\SQLdata on a second server even if the directory in question does not exist.
Can anybody shed any light on this? I am having trouble searching for solutions as the terms I need to search for give me instructional pages rather than problem posting
View Complete Post