File Paths used by upgrade - by JanetB1

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 350133 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 6/9/2008 4:36:04 PM
Access Restriction Public


We are testing upgrades from SQL Server 2005 to SQL Server 2008 and  have run into some problems with the paths.

For a cluster, the file path for SQLBinRoot was F:\MSSQL.1\MSSQL\Binn.  After the upgrade, the path is changed to C:\MSSQL10.MSSQLSERVER\.  The upgrade cannot change the drive letter location of SQLBinRoot and other SQL drives.  It needs to leave the files on the F: drive.

For a standalone server, SQLBinRoot was F:\MSSQL.1\MSSQL\Binn.  After the upgrade, the path is changed to  F:\MSSQL10.MSSQLSERVER\MSSQL\Binn, as expected.  However, our standard installation puts the SQLDataRoot and other paths on another location:  F:\SQLCatalog\MSSQL.1\MSSQL.  After the upgrade, it is using the same MSSQL.1 location.  I expected it to change to the MSSQL10.MSSQLSERVER format.  
Sign in to post a comment.
Posted by Microsoft on 6/26/2008 at 2:33 PM
We have verified the fix for RTM and closed this bug.

Thanks again for your feedback!

Amy Lewis
Posted by Microsoft on 6/25/2008 at 7:58 AM
Janet -

We have fixed this issue for RTM. Thanks for your feedback!


Amy Lewis
Posted by Microsoft on 6/12/2008 at 10:36 AM
Hi Janet,

As we investigated this issue, we also repro'ed the same problem.

However, although the UI shows C:\ drive as the binary installation location for the new upgraded instance, they are actually placed in the F:\ drive.

Do you still have the logs from our test and attach them to this bug? Could you also check if binaries from the upgrade have been really placed in the C:\ drive or F:\ drive?