Home Dashboard Directory Help
Search

SQL Server 2008 Copy Database Wizard by GURSETHI


Status: 

Closed
 as Won't Fix Help for as Won't Fix


1
0
Sign in
to vote
Type: Bug
ID: 676002
Opened: 6/19/2011 9:35:05 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Hi Microsoft,

I am noticing a problem while using COPY DATABASE WIZARD in SQL Server 2008 (10.00.2573). What i did is changed Default Data & Log file location for SQL Instance by right clicking on INSTANCE -> Properties and then Database Settings option.

eg: OLD PATH: C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8\MSSQL\DATA
     NEW PATH: C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8\MSSQL\DATA1

( I created DATA1 folder manually at this location).

Next i opened FACET property for the instance, over there it shows me new path i.e.
C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8\MSSQL\DATA1

Then I restarted SQL Instance so that these changes should be submitted permanently.

Next I tried to create a new database and its getting created to new location i.e. C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8\MSSQL\DATA1 location.

Next I created a sample table and inserted few rows.

I started COPY DATABASE WIZARD and selected SOURCE & DESTINATION server same & selceted this newly created database and used COPY option. It shows me a name say DBNAME_NEW but strange part is that DATABASE FILE & LOG FILE location is still pointing to old i.e. C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8\MSSQL\DATA. Howerver I have made a change and as per that it should point to C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8\MSSQL\DATA1 location.

I though might be its taking this location from SOURCE database which I am trying to copy but that is also not the case as its created after changing DATA & LOG File location and its files are there in C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2K8\MSSQL\DATA1 location?

So why is this behaviour? Is this a bug? Please let me know about this.

Regards
Gurpreet Singh Sethi
Details
Sign in to post a comment.
Posted by Microsoft on 6/30/2011 at 3:21 AM
Hi,

We took a look at this bug along with several others recently. Unfortunately, triaging it against other critical bugs, I do not think we would get to investigating this in the near future. However, we have taken note of this internally, and when we revisit this functionality in the future, we will try and get this resolved.

Thanks for writing in to Microsoft.

Cheers,
Manish
Sign in to post a workaround.