-
Title
Toad for SQL Server 5.5 is incorrectly assuming the .LDF location in an attach operation -
Description
GCMA database needed to moved to another drive. The current file and drive location is E:\MSSQL\Data\GCMA_1.mdf .
GCMA was Detached and moved from the E:\ drive to a like folder on the G:\ drive.
Toad for SQL Server 5.5 was instructed to look on the G:\ where it found G:\MSSQL\Data\GCMA_1.mdf
In review of the attach syntax, it was noticed that Toad for SQL Server 5.5 incorrectly assumed the log file was also going to be at location G:\MSSQL\Data\GCMA_2.ldf
However, the LDF was not moved from F:\MSSQL\Data\GCMA_2.ldf, thus building an attach script syntax that would have failed, because the LDF found was not on the G:\ drive.
I checked with SQL Server Management Studio and found that it knew where the LDF was correctly located and built the attach script syntax correctly.Toad for SQL Server 5.5 should not be assuming the location of the LDF file, meaning it should not just be arbitrarily assigning the location of the LDF file based on the attach location of the MDF file.
The level of assumption that the LDF file is on the same drive as the MDF does not follow good SQL Server data file management best practices.
It should be noted that SS2008R2 did not get this wrong, it left the location of the LDF file alone or up to the user at the time of the attach.
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.